Hi, On Fri, 11 Jan 2008, Kevin Ballard wrote: > On Jan 11, 2008, at 4:29 PM, Johannes Schindelin wrote: > > > If you are serious about this problem, I can give you tons of pointers > > how to go solve it. (Although I might be disconnected this weekend, > > because of the lack of competence of the IT department here.) > > I think I've got a handle on it. I've already expunged the mis-cased > file using git-rebase to remove the offending commit, now I just need to > rewrite the second commit's message so it looks like the original commit > (luckily I didn't do any work in the directory before I re-cased it). > Thanks anyway. I was not talking about fixing it up in your repository. If you really think that git should help you, you gotta teach it to. Because people who do not experience the same as you will be less likely to feel the urge to teach git to help in that situation (because they did not experience that situation yet). For example, I am one of these people. And I guess a lot of these people hang out on this list. 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
