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:24 UTC
Message-ID
<7vy78cu2kt.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<20080321023303.GE1613@coredump.intra.peff.net>
Jeff King <peff@peff.net> writes:
>   2. This can actually be _more_ network intensive than your proposal.

I do not think this matters much in practice. If you have tons of refs on _your_ side to matter, some of them would be tags that are known to both ends. The only case it really is troublesome is when the sender does not know _any_ of the refs the receiver presented to it.

In the illustration in the message you are responding to, if the commit A was tagged at the shared repository when two developers cloned, it does not matter if C is unknown to the second pusher.

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.

Previous: Jeff KingNext: Jeff King
Message 3 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.