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

[PATCH 0/4] Spend more effort in git-fetch-pack finding common revisions

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Oct 23, 2005, 01:35 UTC
Message-ID
<Pine.LNX.4.63.0510230334410.21239@wbgn013.biozentrum.uni-wuerzburg.de>

This series of 4 patches extends the fetch-pack/upload-pack protocol such that more than just one common revision is used to find out which objects are needed by the client.

This means that the client spends more time on enumerating candidates, and the server just acknowledges those it knows about. That is done until the client runs out of candidates, or the server got HAS_MAX common revisions.

While it does not make much of a difference when you are tracking one linear branch on one repository, this change should make it more efficient (and also ease the burden on the server) to work with several repositories having several branches, and intertwined development.

Next thing I'll do is write some nasty test cases.

Flame on, Dscho

Message 1 of 1 in “Spend more effort in git-fetch-pack finding common revisions”
  1. 0/4 Spend more effort in git-fetch-pack finding common revisionsJohannes Schindelin, Oct 23, 2005

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.