[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Windows with Dir/ and dir/

From: Spiro Trikaliotis
Subject: Windows with Dir/ and dir/
Date: Sun, 18 Apr 2004 18:37:32 +0200
User-agent: Mutt/

Hello (again),

I'm using cvs 1.11.1 (debian/stable) on the server, and cvs 1.11.1
(Debian/stable) and cvs 1.11.6 (cygwin) on the client side.  I use
access method ssh to access my remote repository.

I found a somehow "confusing" behaviour which I cannot understand.
Possibly, someone can help me around it. I checked the list archive, and
although there is much on the Windows case-insensitiveness, I did not
find my particular problem mentioned.

I have a repository in which a module contains the following files:


module/Dir itself is empty (except for the subdir Attic/)

As you can see, the two directories differ in the case only.

Everything from Dir/ has been moved to dir/ many revisions before, so
Dir/ has everything contained inside of it in the Attic, and both Dir/
and dir/ contain the same files.

If I checkout -P from the Linux machine, everything works fine and I get
the files module/dir/1 and module/dir/2.

Anyway, if I do a checkout (again, with -P) from the Windows machine, I
get the following files:


but the files 1 and 2 have the contents of the files which are in
module/dir/1 and module/dir/2!

I know and understand that Windows is case insensitive, but this
behaviour is very surprising to me. I would have expected that the
Windows (cygwin) version of CVS creates exactly the files with the case
that it used to check the files out, nothing else). Even the file
module/dir/CVS/Repository points to module/Dir (and not to module/dir
which I would have expected).

I thought -P would not created to obsolete Dir/ but directly the new
dir/. This does not seem to be the case. Does CVS generate a Dir/ and
not remove it until dir/ wants to be written, in which case dir/ would
use the "old" Dir/ on Windows? I thought at first, but as CVS/Repository
points to Dir/, I don't think this is the case.

I have not checked what happens if I commit anything in this case since
I don't want to havoc my repository. Anyway, if I do a cvs release -d, I
get the following message:

$ cvs release vice
address@hidden's password:
address@hidden's password:
cvs server: src/arch/os2/Snippets/ is no longer in the repository
cvs server: src/arch/os2/Snippets/ is no longer in the repository
You have [0] altered files in this repository.
Are you sure you want to release (and delete) directory `vice': yes
address@hidden's password:
cvs release: no such directory: vice

(BTW: What's behind the last "cvs release: no such directory"?)

If you want to know why I have to input my password 3 times, see the
mail I just wrote before. ;-)

Best regards,

Spiro R. Trikaliotis

reply via email to

[Prev in Thread] Current Thread [Next in Thread]