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
Nicolas Pitre <nico@cam.org>
Date
Feb 6, 2008, 20:07 UTC
Message-ID
<alpine.LFD.1.00.0802061505390.2732@xanadu.home>
In-Reply-To
<e1dab3980802061157r36dfa8b9uab49af013cb8e963@mail.gmail.com>
On Wed, 6 Feb 2008, David Tweed wrote:
> Given I'm the only person (AFAICS from the list archives) who's ever
> talked about failed temporary packs, I assume that almost everyone
> using git is using filesystems with sufficient space that they don't
> get write errors,

Note that doing ^C during a fetch will also leave a temporary pack file there. So your patch is good even for people with plenty of disk space.

> so the path building will generally be done 0 times
> per --prune. (Using a USB disk that's almost full, along with
> occasionally filling up my /home with experiment output, is the
> occasions I get them.) So I don't think efficiency is an issue.
Clearly not a hot path indeed.
Nicolas
Previous: David TweedNext: Brandon Casey
Message 13 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.