From: Junio C Hamano <gitster@pobox.com>
Date: Thu, 16 Oct 2014 16:36:34 GMT
Subject: Re: fsck option to remove corrupt objects - why/why not?
Message-ID: <xmqq8ukgug31.fsf@gitster.dls.corp.google.com>
In-Reply-To: <CALKQrgda8mVbqP5=Ag8juN9HMQp7iQ9eDJETfRJe1b0taAFGkg@mail.gmail.com>

Johan Herland <johan@herland.net> writes:

> I simply copied the packfile containing the good copy into the
> corrupted repo, and then ran a "git gc", which "happened" to use the
> good copy of the corrupted object and complete successfully (instead
> of barfing on the bad copy). The GC then removed the old
> (now-obsolete) packfiles, and thus the corruption was gone.
>
> However, exactly _why_ git happened to prefer the good copy in my
> copied packfile instead of the bad copy in the existing packfile, I do
> not know.

By design ;-)