On Tue, Sep 8, 2009 at 02:02, Kevin Grover<kevin_at_kevingrover.net> wrote:
> I have a strange thing happen.
> Subversion 1.5.4 (Ubuntu 9.04)
> On FAT under Linux, If I checkout a WC with a directory that is in all
> uppercase, it changes the case to lowercase. However, if I check the same
> directory out to an ext3 file system, the case is correct. (Or if I do the
> check out under Windows)
> for Example:
> $ svn co file:///media/truecrypt1/repos/svn/notes/trunk notes
> A notes/Publications
> A notes/Publications/ISRI
> A notes/Publications/ISRI/AR-93.pdf
> $ svn st notes
> ? notes/Publications/isri
> ! notes/Publications/ISRI
> However, it all works as expected when I run it from a Windows machine. I
> played around with the directory and I can rename it to mixed case 'IsRi'
> etc, but if I use a 'mv isri i; mv i ISRI; ls' I see 'isri'.
> Anyway, I know FAT is case sensitive (hence the temp file in the rename
> example in the last paragraph), but I though it was case preserving. It
> there something I'm missing about FAT under Linux or is this the expected
FAT is odd WRT its handling of case in file names. Classic 8.3 file
names are case *in*sensitive and case clobbering. The directory table
stores only upper-case. To this day files with especially short names
on windows (XP) will spontaneously upper-case themselves for this
Presumably, the linux FAT implementation chose to present such case
clobbered files in lower case, since the case information is lost in
any case and lowercase is a more common convention on *nix systems,
but I'm just guessing.
FAT with long file name support. (e.g. FAT32) is case *in*senstive,
but case preserving.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-09-08 11:10:37 CEST