Quoting Hannu Koivisto <azure@xxxxxx>: <snip>
Kernel source contains pairs of files whose names differ only by case. Windows cannot store such pairs (at least by default) and apparently there is no support for such a situation in git so you'll only get one file from each pair to your workspace and the other file is shown as modified.
Could git be modified to allow such repositories to be used on windows by locking files that are problematic, for example, a given repository could have files 'AAA' and 'aAa'.
The one that correctly represents the on-disk file would be 'open for edit', while the other file would be locked. To edit the other file, the existing file would need to be locked, and then the other file would then need to be open for edit.
This could even be extended to allow one to "open file AAA for edit as aAa.v2', giving the file an alternate name.
Such a workflow would only need to be used for such files, and could also be used when there are incompatible file names for that given partition type.
-- 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
