On Tue, Jul 7, 2009 at 3:22 PM, Junio C Hamano<gitster@xxxxxxxxx> wrote: > You notice > that you screwed up the configuration to use your peculiar work tree > representation, and you fix it once and for all. A kinda dim-witted question: So what's the best way of "fixing once and for all" a repo infected with carriage returns when you want to use autocrlf=true moving forward? And a hopefully less annoying one: Would you accept a patch explaining how "git reset --hard" doesn't actually rebuild the index from scratch, and how "git read-head" might be recommended in some weird situations? -- 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