I haven't met a VCS which works on both Windows and Unix where case
sensitivity/case insensitivity isn't a problem. A lot of time, it
merely depends upon the back end repository.
I have a Subversion hook that can be used to ban the creation of files
with certain regular expressions in their names. Maybe simply ban all
uppercase letters in a repository that is used by both Unix and
Windows? That is, you can have a file named foo.c, but not Foo.c or
FOO.C. Will this cause more problems than it will solve?
On 8/19/05, Janulewicz, Matthew <MJanulewicz@westernasset.com> wrote:
>
>
> On 8/19/05, Evan Stark <EStark@point-inc.com> wrote:
> > > It's not a solution at all, because that would mean windows clients can
> > > no longer communicate with unix servers and vice versa.
> >
> > Question I've always wondered, does anyone ever really name two different
> > files with the same name but different case? What's the scenario?
>
>
>
> I haven't seen this happen on purpose, but it does happen as others have described.
> At my previous job we used Perforce. We snuck it in on a Linux server, which didn't care about case. Folks would pass around files (build.bat, Version.txt) and check it in with a different case for whatever reason. So we had a bunch of instances where the same directory had Version.txt and version.txt, build.bat, Build.bat and BUILD.BAT. In many cases the files were the same and folks just checked them in for basically no reason, but that's how the tree ended up.
> So IT finds out we have a Linux server and makes us get rid of it. Perforce uses BDB and stores the archives in a sort of in-place tree, so you can imagine what happened when I zipped that baby up and tried to unzip it on a Windows server. Well, maybe you can't imagine if you haven't used Perforce. Basically, the checkpoints did not match up to the tree (version.txt overwrote Version.txt, etc.) so there were many cases of missing files.
> So, it does happen, but usually not on purpose.
> Another curious thing I have come across is MS Visual Studio 6 allowed you to add files to a project with case sensitivity in tact. You could, for instance, add StdAfx.h and stdafx.h to the same project, and it would let you. In some cases the two files were in different directories and worked fine. One time (and this drove me nuts for a long time before I figured it out) the files were in the same directory, and one would constantly overwrite the other. You could also, at the time, have same-named files in differend projects, pointing to the same real filesystem file, with one constantly overwriting the other. I seem to recall (this was some years ago) that this was partially a side effect of the MS SCCS integration with ClearCase. It was basically a big mess, but in most cases not a nutty developer, per se.
>
>
> -Matt
>
>
> **********************************************************************
> E-mail sent through the Internet is not secure. Western Asset therefore recommends that you do not send any confidential or sensitive information to us via electronic mail, including social security numbers, account numbers, or personal identification numbers. Delivery, and or timely delivery of Internet mail is not guaranteed. Western Asset therefore recommends that you do not send time sensitive or action-oriented messages to us via electronic mail.
> **********************************************************************
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
--
--
David Weintraub
qazwart@gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Aug 19 20:59:54 2005