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

Re: [PATCH] Do not call git-rev-list from git-fetch-pack

From
Junio C Hamano <junkio@cox.net>
Date
Oct 21, 2005, 21:32 UTC
Message-ID
<7vbr1iv9nz.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<Pine.LNX.4.63.0510212134570.5542@wbgn013.biozentrum.uni-wuerzburg.de>
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> Yes. This makes it more simple, and is very efficient in the common case. 
> How about increasing MAX_HAS to 64?

The other day I saw HPA tried to sneak in a change to increase it to 64, mingled with other changes. I think increasing it makes sense.

Now the question is, if we count MAX_HAS on the fetch-pack side, how would we coordinate that value with the real limit the other end uses. I guess that would not matter too much. It would not affect the correctness anyway.

Previous: Johannes SchindelinNext: Johannes Schindelin
Message 6 of 9 in “Do not call git-rev-list from git-fetch-pack”
  1. Do not call git-rev-list from git-fetch-packJohannes Schindelin, Oct 21, 2005
  2. Junio C HamanoOct 21, 2005
  3. Johannes SchindelinOct 21, 2005
  4. Junio C HamanoOct 21, 2005
  5. Johannes SchindelinOct 21, 2005
  6. Junio C HamanoOct 21, 2005
  7. Johannes SchindelinOct 22, 2005
  8. Daniel BarkalowOct 21, 2005
  9. Johannes SchindelinOct 21, 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.