From: Junio C Hamano <gitster@pobox.com>
To: Johan Herland <johan@herland.net>
Cc: Ben Aveling <bena.001@optusnet.com.au>,
Git mailing list <git@vger.kernel.org>
Subject: Re: fsck option to remove corrupt objects - why/why not?
Date: Thu, 16 Oct 2014 09:36:34 -0700 [thread overview]
Message-ID: <xmqq8ukgug31.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <CALKQrgda8mVbqP5=Ag8juN9HMQp7iQ9eDJETfRJe1b0taAFGkg@mail.gmail.com> (Johan Herland's message of "Thu, 16 Oct 2014 11:04:04 +0200")
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 ;-)
next prev parent reply other threads:[~2014-10-16 16:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20141015234637.9B4FC781EFB@mail110.syd.optusnet.com.au>
2014-10-16 0:13 ` fsck option to remove corrupt objects - why/why not? Ben Aveling
2014-10-16 9:04 ` Johan Herland
2014-10-16 12:25 ` Jeff King
2014-10-16 12:48 ` Johan Herland
2014-10-16 16:36 ` Junio C Hamano [this message]
2014-10-16 11:59 ` Matthieu Moy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqq8ukgug31.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=bena.001@optusnet.com.au \
--cc=git@vger.kernel.org \
--cc=johan@herland.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.