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

Re: [PATCH] gc --auto: warn garbage collection happens soon

From
Junio C Hamano <gitster@pobox.com>
Date
Dec 28, 2011, 20:02 UTC
Message-ID
<7vfwg41n3p.fsf@alter.siamese.dyndns.org>
In-Reply-To
<20111228184000.GA18780@sigill.intra.peff.net>
Jeff King <peff@peff.net> writes:
Show 6 quoted lines
> [1] Actually, it's not just having objects. You may have just exploded
>     unreachable objects from a pack, but they are still younger than the
>     2 week expiration period. Therefore trying to prune them is
>     pointless, because even if they are unreachable, you won't delete
>     them. So you really want to say "how many actual candidate objects
>     do we have for pruning?"

An obvious knee-jerk reaction is "Ugh, if we have very recently repacked, don't we know what are reachable and what are not already, and use that knowledge while pruning to avoid traversing everything again?"

My memory around repack, fsck and prune needs refreshing, though, to tell if that suggestion is feasible.

Previous: Jeff KingNext: Jeff King
Message 4 of 8 in “gc --auto: warn garbage collection happens soon”
  1. gc --auto: warn garbage collection happens soonNguyễn Thái Ngọc Duy, Dec 27, 2011
  2. Junio C HamanoDec 27, 2011
  3. Jeff KingDec 28, 2011
  4. Junio C HamanoDec 28, 2011
  5. Jeff KingDec 28, 2011
  6. Nguyen Thai Ngoc DuyDec 28, 2011
  7. Nguyen Thai Ngoc DuyDec 28, 2011
  8. Mark BrownDec 29, 2011

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.