Am 26.02.2011 19:13, schrieb Antoine Pitrou: > >> In Mercurial, it's just a hook, and optional. So we can't be sure all >> users use it correctly - and in my (limited) experience with Mercurial, >> chances are high that users will make mistakes in that respect (i.e. >> in one out of one cross-platform projects, a committer had issues >> with CRLF, leading to catastrophic repository corruption). > > “Catastrophic” repository “corruption”? This sounds very strongly like > an urban legend. > Perhaps some files had later to be fixed. But that shouldn't be out of > the realm of normal Mercurial commands (aka "edit file to fix endings, > then hg commit and hg push").
It actually happened to me, so please trust me that it's not a legend. Yes, I could fix it with hg commands, and a lot of text editing. It took me a day, I considered the repository corrupted so that I actually had to branch from the last ok revision, and redo all checkins since (I also discarded changes which I didn't chose to redo). It was a real catastrophe to me. Since the changes actually changed all lines, "hg blame" became useless, which was unacceptable. Regards, Martin _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
