Hi, On Tue, 28 Aug 2007, Reece Dunn wrote: > On 28/08/07, Andreas Ericsson <ae@xxxxxx> wrote: > > > It's going to remain in the state it is, although I disagree that that > > state is broken. Adding case-sensitivity to a content tracker on a > > case-insensitive file system would be quite a lot of work for a very > > small gain. > > I'm not suggesting adding case sensitivity to the content tracker. You don't need to: git handles case sensitivity quite fine, thank you. > > As usual, should you present some small and elegant piece of code that > > makes git capable of dealing with this while running with no slowdown > > at all on sane systems, I'm sure it'd be accepted, or at least very > > thoroughly discussed by the heavy names on the list. > > I have tried the following: > > git mv foo foo.tmp > git mv foo.tmp Foo > > which correctly reports: > > renamed: foo -> Foo > > > Without the code, it's just an ugly can of worms that nobody wants to > > open. > > I haven't got any code yet, but from the analysis above, it would be a > special case in the mv command when the files are the same and the > case is different. > > However, given that the double move works as expected, I don't see this > as being a big issue. The problem is _really_ the filesystem, as you experienced. You just cannot do an "mv foo Foo". You cannot. And that is _exactly_ the problem you experience with git, since at some point, git tries exactly that: "mv foo Foo". So it really, really, really is not a git problem. Just as I told you in my other reply. Ciao, Dscho - 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
