git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git gc taking forever to reflog expire --all

From
GBGeert Bosch <bosch@adacore.com>
Date
May 11, 2010, 10:05 UTC
Message-ID
<3924516F-2626-41C0-8648-47A9481FA09F@adacore.com>
In-Reply-To
<20100511050134.GA9413@coredump.intra.peff.net>
On May 11, 2010, at 01:01, Jeff King wrote:
Show 10 quoted lines
> On Mon, May 10, 2010 at 01:58:11PM -0400, Geert Bosch wrote:
> 
>> On my recent MacBook Pro, I gave up after reflog expire --all
>> had chewed up 30 minutes of perfectly fine CPU time.
> 
> 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

What would be the easiest way for me to repack my repository without running reflog expire at all?

  -Geert
Previous: Jeff KingNext: Jeff King
Message 3 of 5 in “git gc taking forever to reflog expire --all”
  1. Geert BoschMay 10, 2010
  2. Jeff KingMay 11, 2010
  3. Geert BoschMay 11, 2010
  4. Jeff KingMay 11, 2010
  5. Jeff KingMay 11, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.