Case problem
Hi all I work with cvs 1.11.1p1 on NT4.0 with a local repository. Usually it works quite well. But sometimes it has a problem with filename cases like the following: cvs.exe -q -n update N:\Temp\Pec3kcvs4 U N:\Temp\Pec3kcvs4/OS/Src/CINOSFixed32.cpp U N:\Temp\Pec3kcvs4/Os/Src/CINOSFixed32.cpp cvs.exe update: warning: N:\Temp\Pec3kcvs4/OS/Src/CINOSFixed32.cpp was lost cvs.exe update: warning: N:\Temp\Pec3kcvs4/Os/Src/CINOSFixed32.cpp was lost I found out that this can happen if the name in Entries (here OS) is written with different case than the actual file-/dirname, or maybe the checked in name. I don't know why cvs looks at this file/dir twice, but it does it with different case and doesn't recognize the "same" filename. No need to tell me that *ix is case sensitive whereas Windoze is not. I believe I once read about a switch to tell cvs to behave case-insensitive... or maybe not :) bye Fabi ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
CVS case problem
Hi guys, I've a problem, I have a lot of files with the same name but with different case in the same directory, since I working on UNIX there is not a problem, but now when I tried to check out on NT this return a Conflict and this is fine because cvs try to check out 2 files with the same name but with different content. i.e. /home/makefile /home/Makefile /home/slist.cpp /home/SList.cpp unfortunately these files have a dependencies and I can't removed it, is there a way to caught the exit status to say "harmless error" ?? Thanks. Any help is really appreciated. Moises ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
WinCVS case problem
Hello! I am using WinCVS 11b4 I have the following problem: when a file is created with a mixed-case (upper/lower) name, e.g. BuildFlow.html After I add it to cvs and commit, in the repository I see the file buildflow.html Therefore, this is a conflict (because windows ignores case), and I can not update. On the other hand, the file appears as not in CVS. Did someone else encounter a similiar behaviour? Anyway, it would be helpful if WinCVS would recognise this problem (when new and old file names are identical except for the problem) and either try to handle it somehow, or give a meaningful message. Thanks, MST -- This message content is not part of Intel's views or affairs Michael S. Tsirkin > Four things are to be strengthened: Torah,and good deeds, > prayer and one's good manners (Berachoth)
Re: CVS case problem
Zanabria, Moises wrote: I've a problem, I have a lot of files with the same name but with different case in the same directory, since I working on UNIX there is not a problem, but now when I tried to check out on NT this return a Conflict and this is fine because cvs try to check out 2 files with the same name but with different content. Yes. You can't do this. There is no workaround. You must either rename some files, abandon Windows, or make a workaround in your own process. /|/|ike ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: CVS case problem
> > > I've a problem, I have a lot of files with the same name but with different > > case in the same directory, since I working on UNIX there is not a problem, > > but now when I tried to check out on NT this return a Conflict and this is > > fine because cvs try to check out 2 files with the same name but with > > different content. > > Yes. You can't do this. There is no workaround. You must either > rename some files, abandon Windows, or make a workaround in your own > process. Also - make sure your windows editor maintains the case - the windows file systems will actually maintain the case of the filenames (even if it doesn't make them significant), but many(some?) editors will do stupid things like capitalize the filenames before writing it back out. > > > /|/|ike > > > > ___ > Info-cvs mailing list > [EMAIL PROTECTED] > http://mail.gnu.org/mailman/listinfo/info-cvs ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: WinCVS case problem
There is at least one exception to case preservation, if you explicitly add the file: myFile.txt with the command cvs add myfile.txt When I then delete the mixed case file and then do an update, I get myfile.txt Then the file will be added to cvs as myfile.txt. It seems that the command line case overrides the file's case. Found this in 1.10.8 command line, and may be related to specific adds in wincvs, haven't tested it. -Chris -Original Message- From: Alexandre Parenteau [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 29, 2000 10:24 AM To: Michael S. Tsirkin Cc: [EMAIL PROTECTED] Subject: Re: WinCVS case problem Michael, "Michael S. Tsirkin" wrote: > Hello! > I am using WinCVS 11b4 > I have the following problem: > when a file is created with a mixed-case > (upper/lower) name, e.g. BuildFlow.html cvs (and WinCvs) are case-preserving and case-insensitive on Windows. It means that if you had a file "BuildFlow.html", it garantees that the server get a file named "BuildFlow.html", and not "buildflow.html". On the other hand, when the client receives the file, it uses "BuildFlow.html" as the name. Now how it's displayed in the explorer is up to the explorer/filesystem. We get that all the time with cvs on Windows, it should work fine. *But* you cannot have in the same directory two files which differ only by the case upper/lower, that's the only restriction I know of. Regards, alex. > > After I add it to cvs and commit, in the repository > I see the file buildflow.html > > Therefore, this is a conflict (because windows > ignores case), and I can not update. > On the other hand, the file appears as not in CVS. > > Did someone else encounter a similiar behaviour? > > Anyway, it would be helpful if WinCVS would > recognise this problem (when new and old file names > are identical except for the problem) > and either try to handle it somehow, or give a > meaningful message. > > Thanks, > MST > > -- > This message content is not part of Intel's views or affairs > Michael S. Tsirkin > > Four things are to be strengthened: Torah,and good deeds, > > prayer and one's good manners (Berachoth)
Re: WinCVS case problem
Hi Michael, "Michael S. Tsirkin" schrieb: > I am using WinCVS 11b4 > I have the following problem: > when a file is created with a mixed-case > (upper/lower) name, e.g. BuildFlow.html > > After I add it to cvs and commit, in the repository > I see the file buildflow.html Which sort of repository access do you use and where is your repository located? I got a similar situation when I tried to copy files from Windows to a locally mounted Unix "drive" (via ASU). All file names were converted to lower case by ASU - the same situation with Samba on a Linux server however worked fine. So if you use (Win)CVS to access a Unix repository via local mode in such an environment you may get the same problems with CVS as I got with simply copying files. You may consider to use one of the client/server modes instead. At least with pserver I didn't get such problems. Best regards Martin
Re: WinCVS case problem
Michael, "Michael S. Tsirkin" wrote: > Hello! > I am using WinCVS 11b4 > I have the following problem: > when a file is created with a mixed-case > (upper/lower) name, e.g. BuildFlow.html cvs (and WinCvs) are case-preserving and case-insensitive on Windows. It means that if you had a file "BuildFlow.html", it garantees that the server get a file named "BuildFlow.html", and not "buildflow.html". On the other hand, when the client receives the file, it uses "BuildFlow.html" as the name. Now how it's displayed in the explorer is up to the explorer/filesystem. We get that all the time with cvs on Windows, it should work fine. *But* you cannot have in the same directory two files which differ only by the case upper/lower, that's the only restriction I know of. Regards, alex. > > After I add it to cvs and commit, in the repository > I see the file buildflow.html > > Therefore, this is a conflict (because windows > ignores case), and I can not update. > On the other hand, the file appears as not in CVS. > > Did someone else encounter a similiar behaviour? > > Anyway, it would be helpful if WinCVS would > recognise this problem (when new and old file names > are identical except for the problem) > and either try to handle it somehow, or give a > meaningful message. > > Thanks, > MST > > -- > This message content is not part of Intel's views or affairs > Michael S. Tsirkin > > Four things are to be strengthened: Torah,and good deeds, > > prayer and one's good manners (Berachoth)
