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

Summer of Code - Cached Packs/Object Lists

From
Tthisnukes4u@gmail.com <thisnukes4u@gmail.com>
Date
Mar 23, 2009, 01:53 UTC
Message-ID
<fsmi80et2dp57f5bdxUYAxe124vaj_firegpg@mail.gmail.com>
Hey list,
     My name is Thomas Coppi, and I am a junior studying Computer Science at New Mexico Tech.  I've been using git for a few years now for managing coursework and personal projects, but have never looked much into the git source code or internals, so I figure that Summer of Code is a good way to get started.
     I am particularly interested in the packfile caching project mentioned on the wiki, but I have a couple of questions:
1.  Would it be possible to implement both the packfile and object list caching mechanisms, or might would one interfere with the other in some way?
2.  With just a quick perusal of the daemon source, I noticed that it shells out to the upload-pack command. Where would it be appropriate to implement such a caching mechanism, in the daemon proper, the upload-pack code, or would both need to be updated?
Thanks in advance, and sorry if my questions seem a little bit newbish, as I mentioned this is my first time diving into git internals.
-- 
Thomas Coppi
Next: Shawn O. Pearce
Message 1 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.