From: Jon Seymour <jon.seymour@gmail.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Git Mailing List <git@vger.kernel.org>,
Christian Couder <chriscool@tuxfamily.org>
Subject: Re: RFC: Should git gc/repack respect .git/refs/replace?
Date: Sat, 23 Jul 2011 19:25:50 +1000 [thread overview]
Message-ID: <CAH3Anrqt-s6mPLXw_Uzf0YODFtTPRPJEDgvphjMFxybJibvbPg@mail.gmail.com> (raw)
In-Reply-To: <m2wrf9cq0i.fsf@igel.home>
On Sat, Jul 23, 2011 at 7:20 PM, Andreas Schwab <schwab@linux-m68k.org> wrote:
> Jon Seymour <jon.seymour@gmail.com> writes:
>
>> I recently damaged a USB drive containing an archive of a finished project.
>>
>> I am able to paper over a week of missing history by using the git
>> replace mechanism, so that git rev-list now works as expected.
>>
>> When I run git gc or git repack, I get the following:
>>
>> error: Could not read 023a1d5d3977420ba041cb556c0eee17c326aeb6
>> fatal: Failed to traverse parents of commit
>> 44d578ea81f7a90989e2ee3c676f50e3aff7071f
>
> git-replace(1):
>
> Replacement references will be used by default by all git commands
> except those doing reachability traversal (prune, pack transfer and
> fsck).
>
Oops. Missed that - thanks.
> This is required, since the replaced objects are not supposed to be
> recycled. If you want to make the replacements permanent use git
> filter-branch.
Ah, makes sense.
jon.
next prev parent reply other threads:[~2011-07-23 9:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-23 8:39 RFC: Should git gc/repack respect .git/refs/replace? Jon Seymour
2011-07-23 9:20 ` Andreas Schwab
2011-07-23 9:25 ` Jon Seymour [this message]
2011-07-23 9:22 ` Jakub Narebski
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=CAH3Anrqt-s6mPLXw_Uzf0YODFtTPRPJEDgvphjMFxybJibvbPg@mail.gmail.com \
--to=jon.seymour@gmail.com \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=schwab@linux-m68k.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).