> From: Michael Santos [mailto:[EMAIL PROTECTED]] > Sent: Thursday, October 18, 2001 12:53 PM
> My next question: has the issue with changes in capitalization of > filenames between Windows and Unix client/servers been resolved (e.g., > under Windows, rename file.txt => File.txt, commit File.txt)? What is > the suggested work around for it? > > I can prevent capitalization changes by using a pre-commit > check but I'm > wondering if anyone has a better way. I think not. But you may not have a problem. Really, if all of the clients are under Windows, they will not be able to add files whose names conflict with existing filenames in a case insensitive comparison. If file.txt exists, no one else can add File.txt in the same directory. The problem arises when you have users on Windows and on Unix-like platforms, and someone on Unix adds in a README.TXT where there is already a ReadMe.txt. When a Windows user checks out this directory, things are all screwed up. I prevented this at a previous employer with a script in commitinfo, as you were considering doing. Someone wrote a patch, about a year ago I think, to implement an "addinfo" administrative file. That idea drove some people on this list into conniptions, though. Jerry _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
