From: Jeff King <peff@peff.net>
To: Geert Bosch <bosch@adacore.com>
Cc: git List <git@vger.kernel.org>
Subject: Re: git gc taking forever to reflog expire --all
Date: Tue, 11 May 2010 06:08:00 -0400 [thread overview]
Message-ID: <20100511100800.GA452@coredump.intra.peff.net> (raw)
In-Reply-To: <3924516F-2626-41C0-8648-47A9481FA09F@adacore.com>
On Tue, May 11, 2010 at 06:05:14AM -0400, Geert Bosch wrote:
> > There are some corner cases that can cause the expire-unreachable
> > algorithm to behave badly. The fix is b4ca1db (reflog
> > --expire-unreachable: avoid merge-base computation, 2010-04-07), but
> > hasn't been included in a release yet.
> >
> I tried with v1.7.1 + cherry-pick b4ca1db968eb57d9cd869337bffa254e0b2c83bd,
> but that didn't solve the issue.
> > In the meantime, you can work around it with:
> >
> > git config gc.reflogExpireUnreachable never
>
> I had tried that too, but I guess I'll just have to be very patient:
> 22707 ttys001 11:14.27 git reflog expire --all
Hmm. If that didn't solve it, then presumably it is a different problem,
and I'd like to take a closer look. Is it possible for you to make a
tarball of the .git directory available?
> What would be the easiest way for me to repack my repository
> without running reflog expire at all?
Try "git repack -Ad".
-Peff
next prev parent reply other threads:[~2010-05-11 10:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-10 17:58 git gc taking forever to reflog expire --all Geert Bosch
2010-05-11 5:01 ` Jeff King
2010-05-11 10:05 ` Geert Bosch
2010-05-11 10:08 ` Jeff King [this message]
2010-05-11 15:30 ` Jeff King
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=20100511100800.GA452@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=bosch@adacore.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).