On Sun, Sep 14, 2008 at 8:40 PM, traderhut.com <adwords_at_traderhut.com>wrote:
> Is there any way to turn off case sensitivity for SVN?? I've long
> held, that directories should allow mixed case, but if 'foo.bar' is
> accessed as 'Foo.Bar' it should allow the access. In other words,
> it's OK to store a mixed case name, but don't fail all over yourself
> when someone lower cases or upper cases the filename when you access
> SVN is case sensitive, and for some reason, checking in files
> through TortoiseSVN caused some weirdness in the file names... It
> lowercased one word in the middle of the name, but not the whole name,
> i.e. FooBar.Designer.cs became FooBar.designer.cs -> WTF?? and
> that meant that we ended up getting both 'FooBar.Designer.cs' and
> 'FooBar.designer.cs' checked into the archive... Now, when you create
> an empty directory and pull down the files into it, you get this nice
> error.. that it can't move the file or something like that....
> Wonderful.... I guess it got the files down, and Windows (correctly,
> IMHO) wrote both files to the same file, and then that file got moved
> wherever it was going and the other one didn't exist...
> Anyone who would allow Foo.C and foo.c to be in the same directory
> is just ASKING for trouble, so it simply shouldn't be allowed by SVN
> to get rid of the morons who think Wow! what a wonderful idea.. that
> way when I tell someone to grab foo.c I'll have a 50/50 chance they
> will pull the right one.. Or I can say "get the file Shift/F-o-o-dot-
> Shift/C" and .... What a mess..
Not everyone uses case-insensitive OSes. Sometimes, in UNIX, *.C is used
for C++ and *.c is used for C.
> Anyway, I want to turn it off, is there a way to do it?
The correct way to fix this is to add a pre-commit hook script that checks
that your file case (for each file added) is what you want and reject the
commit (with an appropriate error message) if it is not.
Received on 2008-09-17 04:00:22 CEST