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

Re: Summer of Code - Cached Packs/Object Lists

From
Shawn O. Pearce <spearce@spearce.org>
Date
Mar 23, 2009, 02:52 UTC
Message-ID
<20090323025244.GO23521@spearce.org>
In-Reply-To
<fsmk86y8vqj4f56b08UYAxe124vaj_firegpg@mail.gmail.com>
Thomas Coppi <thisnukes4u@gmail.com> wrote:
Show 10 quoted lines
> On Sun, Mar 22, 2009 at 7:59 PM, Shawn O. Pearce <spearce@spearce.org> wrote:
>> You could do both. ??But I think most people on the list will argue
>> that doing both is overkill and only one is necessary, and further,
>> that only the one that offers the "biggest bank for the buck"
>> should be implemented.
>
> Alright, that seems reasonable.  Given that I think I would lean
> towards implementing an object list caching mechanism, since that seems
> to be more generally applicable.  The logic for this would then need to
> be in the rev-list code(as mentioned in the JGit discussion), correct?

Probably. IIRC upload-pack forks a rev-list to produce the object list, and pipes that into the forked pack-objects' stdin. Thus rev-list is probably what would need to know how to include the cached list to its output.

-- 
Shawn.
Previous: Thomas CoppiNext: Nicolas Pitre
Message 4 of 5 in “Summer of Code - Cached Packs/Object Lists”
  1. thisnukes4u@gmail.comMar 23, 2009
  2. Shawn O. PearceMar 23, 2009
  3. Thomas CoppiMar 23, 2009
  4. Shawn O. PearceMar 23, 2009
  5. Nicolas PitreMar 23, 2009

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.