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

Re: [PATCH] prune: heed --expire for stale packs, add a test

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 6, 2008, 05:15 UTC
Message-ID
<7v7ihi64xm.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<alpine.LFD.1.00.0802051512370.2732@xanadu.home>
Nicolas Pitre <nico@cam.org> writes:
Show 15 quoted lines
> On Tue, 5 Feb 2008, Johannes Schindelin wrote:
>
>> Follow the same logic as for loose objects when removing stale packs: they
>> might be in use (for example when fetching, or repacking in a cron job),
>> so give the user a chance to say (via --expire) what is considered too
>> young an age to die for stale packs.
>> 
>> Also add a simple test to verify that the stale packs are actually
>> expired.
>> 
>> Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
>
> Acked-by: Nicolas Pitre <nico@cam.org>
>
> Nicolas

They are not "stale packs", but temporary files that wanted to become pack but did not succeed. Perhaps "stale temporary packs"?

Shouldn't we do something similar to objects/pack/pack-*.temp files and objects/??/*.temp that http walker leaves?

Previous: Nicolas PitreNext: Johannes Schindelin
Message 5 of 20 in “Make git prune remove temporary packs that look like write failures”
  1. Make git prune remove temporary packs that look like write failuresDavid Steven Tweed, Feb 5, 2008
  2. Nicolas PitreFeb 5, 2008
  3. prune: heed --expire for stale packs, add a testJohannes Schindelin, Feb 5, 2008
  4. Nicolas PitreFeb 5, 2008
  5. Junio C HamanoFeb 6, 2008
  6. Johannes SchindelinFeb 6, 2008
  7. Nicolas PitreFeb 6, 2008
  8. Junio C HamanoFeb 6, 2008
  9. Brandon CaseyFeb 6, 2008
  10. David TweedFeb 6, 2008
  11. Brandon CaseyFeb 6, 2008
  12. David TweedFeb 6, 2008
  13. Nicolas PitreFeb 6, 2008
  14. Brandon CaseyFeb 6, 2008
  15. David TweedFeb 6, 2008
  16. Nicolas PitreFeb 6, 2008
  17. David TweedFeb 6, 2008
  18. Nicolas PitreFeb 6, 2008
  19. David TweedFeb 6, 2008
  20. Junio C HamanoFeb 6, 2008

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.