News for hackers. Stuff that matters.
Re:Distrusting git by ajross on Saturday October 01, 2011 @01:20PM (#3060498)
Of course it's not cool. It's a bug, and it was fixed. But the relevancy is to the title and summary. When you say "git destroyed my data" it sounds like you're saying that git lost commited data in the repo.

What actually happened here is that the working tree got clobbered. That is a vastly less problematic situation. Working trees get clobbered all the time: rogue "make clean" changes, system crashes, someone-stole-my-laptop, errant rm -rf, forgetting which tree your changes are in... I've lost working data to every one of these, and I never felt the need to blame my tools in a blog post.

So yeah. It's a bug (and a pretty embarassing one). It was fixed. Is there anything more to say? Move along.

Re:Distrusting git by click170 on Saturday October 01, 2011 @01:35PM (#3060541)
To add, it's commendable that he tracked down the bug himself, at least I think so. Many people would throw their hands up in the air and walk away with a sour disposition, but props to this guy for working it out to the end.
Re:Distrusting git by joe_the_user on Saturday October 01, 2011 @04:26PM (#3061014)
If "make clean" clobbered a source directory without me making an error in my make file, I would be rather miffed.

"All software has bugs, but bugs that destroy data are pretty devastating." It's hard not to agree with this...

Re:Distrusting git by ajross on Saturday October 01, 2011 @10:43PM (#3061863)
The point was more that if you've ever written a "make clean" rule, you've probably blown away your source tree a few times trying to do it. The software development working directory is the wild west. Bugs that destroy data here, frankly, don't rise anywhere near "devastating" in my book, sorry.