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

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

From
Jeff King <peff@peff.net>
Date
May 11, 2010, 05:01 UTC
Message-ID
<20100511050134.GA9413@coredump.intra.peff.net>
In-Reply-To
<0C5B1A89-551A-4EC8-862A-C306A286FAF4@adacore.com>
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.

In the meantime, you can work around it with:
  git config gc.reflogExpireUnreachable never
-Peff
Previous: Geert BoschNext: Geert Bosch
Message 2 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.