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

Re: [PATCH] Make git prune remove temporary packs that look like write failures

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 6, 2008, 10:02 UTC
Message-ID
<7vve52z9lf.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<Pine.GSO.4.63.0802051844220.15867@suma3>
David Steven Tweed <d.s.tweed@reading.ac.uk> writes:
Show 15 quoted lines
> Write errors when repacking (eg, due to out-of-space conditions)
> can leave temporary packs (and possibly other files beginning
> with "tmp_") lying around which no existing
> codepath removes and which aren't obvious to the casual user.
> These can also be multi-megabyte files wasting noticeable space.
> Unfortunately there's no way to definitely tell in builtin-prune
> that a tmp_ file is not being used by a concurrent process.
> However, it is documented that pruning should only be done
> on a quiet repository. The names of removed files are printed.
>
> Signed-off-by: David Tweed (david.tweed@gmail.com)
> ---
>
> Per discussion of previous version, this now unconditionally
> removes any tmp_ file existing when prune is run.
Sorry, can't apply
	Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Previous: David Tweed
Message 20 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.