On 06/15/2011 10:14 AM, Jakub Narebski wrote: > > core.ignorecase:: > If true, this option enables various workarounds to enable > git to work better on filesystems that are not case sensitive, > like FAT. For example, if a directory listing finds > "makefile" when git expects "Makefile", git will assume > it is really the same file, and continue to remember it as > "Makefile". > > The default is false > > But that wouldn't unfortunately help when there are two files which > filename differs only in case. > > You would have to do tricks with `git update-index` and its > --assume-unchanged bit (though perhaps `core.ignorecase` would be > enough) and `--cacheinfo <mode> <object> <path>` together with > `git hash-object -w`... > > Or perhaps delete file which you have in working area, checkout > one file, add it, checkout other file, add it, use 'git commit' > and not 'git commit -a'. > > But that are only possible solutions; I have sane filesystem. > > Can't you work on NTFS, and use USB stick only for transport of > either tarred repository, or bundle? FWIW - NTFS likely does not help here because even though NTFS supports unique-cased filenames, Windows and Win32-apps do not. http://support.microsoft.com/kb/100625 For example, cmd.exe: C:\> touch makefile C:\> copy makefile Makefile The file cannot be copied onto itself. 0 file(s) copied. cygwin/bash: $ touch makefile $ cp makefile Makefile cp: `makefile' and `Makefile' are the same file Linux (on NTFS volume): mnt/NTFS: touch makefile mnt/NTFS: cp makefile Makefile mnt/NTFS: ls *akefile makefile Makefile Mac's "HFS Plus" filesystem supports unique-on-case, but it is not safe to enable it on a boot disk. http://support.apple.com/kb/TA21400?viewlocale=en_US Phil -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html