Moreover, Mercurial's storage scheme is built on append-only files, whereas Git periodically repacks its objects, which means that Mercurial actually has fewer opportunities for cosmic rays to hit the bits while they are in motion, and so less chance of corruption.
Most bit rot isn't due to cosmic rays, but rather to decay on the disk itself.
Re:Prefer mercurial to git
by mdellabitta on Sunday February 16, 2014 @01:40PM
(#7248636)
Apparently, decay on the disk itself is sometimes caused by cosmic rays:
http://docs.oracle.com/cd/E19253-01/819-5461/gbbym/index.htm...
Mercurial was announced on 2005-04-19 and git on 2005-04-07, so no Mercurial was not first.
Edit: Monotone is older than git though.
I think we can state they weren't copying each other.
I think both started on the same day (due to both authors being part of the kernel "kabal" and already in the known about the upcoming bk debacle).
Mercurial was usable earlier though ;-)
(the first git versions were really really low level, and did not include features like packs, while hg had high kevel command line and its compressed storage format from the first release)
git doesn't run fsck on the entire repo for each operation, and unless you fsck or clone you won't detect corruption for quite a while.
it's exactly the same for hg, which is built on the same hashing concept as git (actually the other way round, as hg came first).