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

Re: [RFC/PATCH] gc: do not explode objects which will be immediately pruned

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 11, 2012, 18:31 UTC
Message-ID
<7v398aktme.fsf@alter.siamese.dyndns.org>
In-Reply-To
<alpine.LFD.2.02.1204101623010.16314@xanadu.home>
Nicolas Pitre <nico@fluxnic.net> writes:
Show 13 quoted lines
>> ...
>> This patch teaches pack-objects to receive the expiration
>> information and avoid writing these objects out. It also
>> teaches "git gc" to pass the value of gc.pruneexpire to
>> repack (which in turn learns to pass it along to
>> pack-objects) so that this optimization happens
>> automatically during "git gc" and "git gc --auto".
>> 
>> Signed-off-by: Jeff King <peff@peff.net>
>
> Looks fine to me.
>
> Acked-by: Nicolas Pitre <nico@fluxnic.net>
Thanks, both.
Previous: Nicolas Pitre
Message 3 of 3 in “gc: do not explode objects which will be immediately pruned”
  1. gc: do not explode objects which will be immediately prunedJeff King, Apr 7, 2012
  2. Nicolas PitreApr 10, 2012
  3. Junio C HamanoApr 11, 2012

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.