From: Jeff King <peff@peff.net>
To: Ben Aveling <bena.001@optusnet.com.au>
Cc: Edward Thomson <ethomson@edwardthomson.com>, git@vger.kernel.org
Subject: Re: [RFC/PATCH] fsck: do not canonicalize modes in trees we are checking
Date: Mon, 20 Oct 2014 02:21:57 -0700 [thread overview]
Message-ID: <20141020092157.GC12913@peff.net> (raw)
In-Reply-To: <5443B136.4060009@optusnet.com.au>
On Sun, Oct 19, 2014 at 11:40:22PM +1100, Ben Aveling wrote:
> This seems to have worked. I also had to move away the existing .idx and
> copy in a new one before it was happy.
Sorry if I wasn't clear; you do need to copy the .idx files along with
the packfiles (you can regenerate the .idx files from the packfiles on
the destination, but they're not that big; it's probably easier just to
copy them).
> I'm not sure that what I've done is so different from simply copying the
> other version of the repository - there shouldn't have been anything in the
> corrupt version that wasn't also in the good one. But any rate, it worked.
Right, a valid technique for repairing corruption is to just blow away
the original repo entirely and replace it with a good copy. But this is a
way of ensuring that no commits are missed, and keeping the original set
of refs, config options, and reflogs.
-Peff
prev parent reply other threads:[~2014-10-20 9:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-23 15:47 [RFC/PATCH] fsck: do not canonicalize modes in trees we are checking Jeff King
2014-09-23 16:23 ` Edward Thomson
2014-09-23 16:30 ` Jeff King
2014-10-12 22:37 ` Ben Aveling
2014-10-14 8:21 ` Jeff King
[not found] ` <543F074B.2050907@optusnet.com.au>
2014-10-16 0:20 ` Jeff King
2014-10-19 12:40 ` Ben Aveling
2014-10-20 9:21 ` Jeff King [this message]
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=20141020092157.GC12913@peff.net \
--to=peff@peff.net \
--cc=bena.001@optusnet.com.au \
--cc=ethomson@edwardthomson.com \
--cc=git@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).