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

Re: [PATCH] handle concurrent pruning of packed objects

From
Junio C Hamano <junkio@cox.net>
Date
Jun 2, 2006, 15:53 UTC
Message-ID
<7vwtbzblkf.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<20060602153223.GA4223@coredump.intra.peff.net>
Jeff King <peff@peff.net> writes:
> This is a repost, since there was no response last time. Linus
> indicated this approach was reasonable; see:
>   <Pine.LNX.4.64.0605300752430.5623@g5.osdl.org>
I haven't forgotten about it, but I have been sick.

I am uncertain about not re-examining the packs it originally thought it had. By prepending the new ones (and the same old surviving ones) at the beginning you are effectively hiding the old packs, which sounds reasonable in the usual case.

Also I suspect this might have funny interaction with the case where there are hand-added packs (see how verify-pack does it). We do not silently "fix" missing object problems we discover there.

Previous: Jeff KingNext: Junio C Hamano
Message 2 of 7 in “handle concurrent pruning of packed objects”
  1. handle concurrent pruning of packed objectsJeff King, Jun 2, 2006
  2. Junio C HamanoJun 2, 2006
  3. Junio C HamanoJun 2, 2006
  4. Jeff KingJun 2, 2006
  5. Junio C HamanoJun 2, 2006
  6. sha1_file: avoid re-preparing duplicate packsJeff King, Jun 2, 2006
  7. Linus TorvaldsJun 2, 2006

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.