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

Re: Efficient retrieval of commit log info

From
Eirik Bjørsnøs <eirbjo@gmail.com>
Date
Dec 12, 2007, 15:19 UTC
Message-ID
<34660cca0712120719p2d7cda44s97ab770abd648742@mail.gmail.com>
In-Reply-To
<alpine.LFD.0.99999.0712121001430.555@xanadu.home>
> On the other hand, this is pretty trivial to extend the protocol so only
> commit objects are transferred.  Using 'git log' on the client side
> would work, as long as you don't use any of the content walking options.
Nicolas,
So what you're suggesting is that:
1) git-clone could be changed such that the user could ask not to
fetch content, only commit objects.
2) git-daemon (or the protocol layer, again I'm not familiar with the
implementation) could be changed such that it only sends commit
objects on request.
3) Changes to git-log is not necessary.

Anybody have a clue how much work this would require and if this is something that would be generally useful for the community?

Eirik.
Previous: Nicolas PitreNext: Jon Smirl
Message 4 of 8 in “Efficient retrieval of commit log info”
  1. Eirik BjørsnøsDec 12, 2007
  2. Johannes SchindelinDec 12, 2007
  3. Nicolas PitreDec 12, 2007
  4. Eirik BjørsnøsDec 12, 2007
  5. Jon SmirlDec 12, 2007
  6. Eirik BjørsnøsDec 12, 2007
  7. Santi BéjarDec 12, 2007
  8. Linus TorvaldsDec 12, 2007

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.