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

Re: [PATCH] "git push": tellme-more protocol extension

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 21, 2008, 04:47 UTC
Message-ID
<7viqzgu1iy.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<20080321042821.GA5453@coredump.intra.peff.net>
Jeff King <peff@peff.net> writes:
Show 9 quoted lines
> On Thu, Mar 20, 2008 at 09:24:18PM -0700, Junio C Hamano wrote:
>
>> So a potential improvement might be to ask for "tellme-more" only if we do
>> not know any of the refs the receiver showed us; my patch does it if there
>> is at least one unknown instead.
>
> You can still get cases where doing this is more expensive than your
> patch, because A..B is very small but shared_tag..A is very large. I'm
> not sure which is more likely in practice.

Oh, I have a few fix-ups since I sent the patch, but I am not planning to experiment with _your_ protocol myself. Debugging one protocol extension a week is painful enough ;-)

And tellme-more does not send _every_ commit. The sender asks only about the refs it does not know about, and the receiver sends densely near the tip and then walks sparsely as it goes deeper, so the traffic wouldn't be so bad. Latency might be a different story, though.

Previous: Jeff King
Message 5 of 5 in “"git push": tellme-more protocol extension”
  1. "git push": tellme-more protocol extensionJunio C Hamano, Mar 20, 2008
  2. Jeff KingMar 21, 2008
  3. Junio C HamanoMar 21, 2008
  4. Jeff KingMar 21, 2008
  5. Junio C HamanoMar 21, 2008

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.