Git-windows case sensitive file names not handled properly

Question

We have the git bare repository in unix that has files with same name that differs only in cases.

Example:

GRANT.sql grant.sql 

When we clone the bare repository from unix in to a windows box, git status detects the file as modified. The working tree is loaded only with grant.sql, but git status compares grant.sql and GRANT.sql and shows the file as modified in the working tree.

I tried using the core.ignorecase false but the result is the same.

Is there any way to fix this issue?

Answer 1

Windows is case-insensitive (more precisely, case-preserving). There is simply no possible way for two files to exist whose names only differ in case: two filenames which differ only in case are the same filename. Period.

So, Git is walking the repository, checking out one file after the other, until it hits the first one of the two problem files. Git checks it out, then goes further about its business until it hits the second file. Again, Git checks it out. Since from Windows' point of view the filename is the same as the first one, the first file simply gets overwritten with the second one. Which now makes Git think that the first file was changed to have the same content as the second one.

Note that this has nothing to do with Git: exactly the same would happen if you had a tarball, a zipfile or a Subversion repository.

If you want to do development on multiple different platforms, you have to respect the restrictions of those platforms and you have to confine yourself to the lowest common denominator of all the platforms you support. Windows supports ADS, Linux doesn't. OSX supports resource forks, Windows doesn't. BSD supports case-sensitivity, Windows doesn't. So, you can't use any of those. That's just the way it is.

core.ignorecase isn't going to help you here, because that handles exactly the opposite problem.

Answer 2

I just encountered a similar problem. In my case, the two files with similar names differing only in case were in a subdirectory that wasn't relevant on the Windows clone. Git 1.7 has a sparse checkout feature that lets you exclude certain files from a working copy. To exclude this directory:

git config core.sparsecheckout true echo '*' >.git/info/sparse-checkout echo '!unwanted_dir/' >>.git/info/sparse-checkout git read-tree --reset -u HEAD 

After this, the unwanted_dir/ subdirectory was completely gone from my working copy and Git continues to work with the rest of the files as normal.

If your GRANT.sql and grant.sql are not relevant on the Windows clone, then you can add their names to .git/info/sparse-checkout to exclude those files specifically.