Thomas Ackermann <th.acke...@arcor.de> writes:
> The man-page for git-config says:
> 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"."
> So "various workarounds" does _not_ mean that _all_ filenames are
> processed modulo upper/lower case, or?
Keywords in that paragraph include "various" (not all) and "better"
(not perfectly), and the most important one is "when git expects".
When running "git add file.txt" with "File.txt" in the index, git
expects "File.txt", but the ignorecase logic makes git assume they
are the same, and add content from "file.txt" as "File.txt".
And "git blame $path" probably should expect $path is something that
appear in the tree of HEAD; apparently it does not.
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html