On Mon, Jan 16, 2012 at 7:50 PM, Yves Goergen <nospam.list@xxxxxxxxxxxxxxx> wrote: > It's getting more weird. I believe that (msys)Git doesn't really know > how the filesystem on its operating system works. Git for Windows know how the file-system works, and tries to prevent you from shooting yourself in the leg by being case-insensitive when matching the index and the working copy. But there is an opt-out for this, which is controlled by the configuration option core.ignorecase, which Peff already asked about. This option is supposed to be enabled by default on Windows. What you are describing sounds like that option might have gotten disabled somehow. But it might be something else, see below. > I have made some more > changes now and want to commit them. TortoiseGit reports the files > Form1.Designer.cs and Form1.designer.cs (note the case difference) as > modified and ready to commit. How is that supposed to work? Very speculative comment: This might be a bug in TortoiseGit. Looking at the sources, it seems they are using libgit2 to mess around with the index; perhaps it's case-sensitivity code isn't as well tested as Git for Windows'? For instance, they do their own index and tree sorting, in an attempt to be case sensitive: http://code.google.com/p/tortoisegit/source/diff?spec=svnf151c0ddf205fa1fc1ff886b8cfc4af87d373b26&r=f151c0ddf205fa1fc1ff886b8cfc4af87d373b26&format=side&path=/src/Git/GitIndex.cpp -- 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