Eric Raible [off-list ref] writes:
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?
Didn't "rm -f .git/index && git reset --hard HEAD" work?
And a hopefully less annoying one:
Would you accept a patch explaining how "git reset --hard" doesn't
actually rebuild the index from scratch,...
Absolutely.
... and how "git read-head" might
be recommended in some weird situations?
I am less certain about that; people may have easier-to-read solution than
the one with read-tree, I would suspect.