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

Re: [RFC] git-fetch - repack in the background after fetching

From
Daniel Barkalow <barkalow@iabervon.org>
Date
May 30, 2006, 06:37 UTC
Message-ID
<Pine.LNX.4.64.0605300207130.6713@iabervon.org>
In-Reply-To
<Pine.LNX.4.64.0605292147010.5623@g5.osdl.org>
On Mon, 29 May 2006, Linus Torvalds wrote:
> Some long-running (in git terms) git programs will look up the pack-files 
> when they start, and if you repack after that, they won't see the new 
> pack-file, but they _will_ notice that the unpacked files are no longer 
> there, and will be very unhappy indeed.

We should be able to fix this, right? If an object isn't found in packs or unpacked, look for new packs; if there are any, look for the object in them; if it's not there, then give up. The only tricky thing is making it possible to scan through the available packs without installing any that are already installed. I think the failure case is only a critical path in the history-walking fetch code, which should probably disable this (or defer it to after trying to download the object).

	-Daniel
*This .sig left intentionally blank*
Previous: Martin LanghoffNext: Linus Torvalds
Message 4 of 5 in “[RFC] git-fetch - repack in the background after fetching”
  1. Martin LanghoffMay 30, 2006
  2. Linus TorvaldsMay 30, 2006
  3. Martin LanghoffMay 30, 2006
  4. Daniel BarkalowMay 30, 2006
  5. Linus TorvaldsMay 30, 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.