Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx> writes:
> So I agree, in this case the "remove files that go away first" would work
> around the problem, and we could look into whether that is reasonable in
> some cases, but in general it's not trivial either.
I think we have two phase "remove then create" in git-apply for an
entirely different reason (we do check before doing any removal or
creation).
> My personal guess is that it's probably better to start teaching git about
> case-broken filesystem, even if we start it with some common special case
> rather than getting every case right from the beginning.
Hmm. I have to say I am not very enthused by the prospect, as I agree
with your reasoning in your earlier message why this has been lower
priority ("sane people when forced to use case corrupting systems avoid
problematic paths to make this a non-issue anyway"). My feeling is that
this falls into the "when we are bored to death and have absolutely
nothing better to do" category.
--
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
