On Sat, Mar 22, 2008 at 10:21:05AM -0700, Linus Torvalds wrote: > > - I've tested this series, both on a case-sensitive one (using hardlinks > to test corner cases) and on a vfat filesystem under Linux (which is > case-insensitive and *really* odd wrt case preservation - it remembers > the name of removed files, so it preserves case even across removal and > re-creation!) I also have observed this problem with VFAT on Linux, but the effect was not stable. It looks like old information is preserved somewhere in caches... Anyway, I have tested this series of patches a bit on Windows and so far I have found the following: - merge different branches were two file names are only differ by case will cause that the result branch has two file names that differ only by case and one of them will be overwritten by the other and shown as modified in the worktree by git status. - git status cares only about case-insensitivity only for files and not for directories. Thus, if case of letters in a directory name is changed then this directory will be shown as untracked. - pattern specified in .gitignore are match as case-sensitive despite core.ignorecase set to true. Personally, I don't care about any of the above issues much as I rarely work on Windows and when I do, I always check that all filenames are in low case except Makefile (and a few more exceptions). So, I have never had any problem with using Git on case-insensitive system... Dmitry -- 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
