On Sat, 9 Jun 2007, Thomas Glanzmann wrote:
the machine that had the issues just got down because of a broken power
supply and took half the rack with it. So it was definitive a hardware
fault. Sorry for all the trouble. And the bottom line is: It was _not_
git, it was broken hardware!
Good. That was one of the design goals for git (ie the "you know you can
trust the data" thing relies on very strong protection at all levels,
even in the presense of disk/memory/cpu corruption).
I think we have a pretty good record on this: the only real git-induced
corruption I can remember was the embarrassing bug with use-after-free of
the CRLF auto-translation. But let's not get complacent.
Linus