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

Re: Huge push upload despite only having a tiny change

From
Junio C Hamano <gitster@pobox.com>
Date
Jun 3, 2020, 20:39 UTC
Message-ID
<xmqqpnafriin.fsf@gitster.c.googlers.com>
In-Reply-To
<20200603015314.GA253041@google.com>
Jonathan Nieder <jrnieder@gmail.com> writes:
Show 9 quoted lines
> There is one trick a server can use to mitigate this: advertise some
> refs that don't exist!  If you advertise a ref ".have", then Git
> will understand that the server has that object but it is not an
> actual ref.  Gerrit uses this trick in its HackPushNegotiateHook[1]
> to advertise a few recent commits.
> ...
> Summary: (1) try fetching first (2) let's improve
> HackPushNegotiateHook#advertiseRefs (3) let's improve "git push"
> protocol to make this a problem of the past.

In the meantime, perhaps we can teach receive-pack the same "let's advertise a few recent commits as if they exist as tips of refs" as well?

Previous: Elijah Newren
Message 6 of 6 in “Huge push upload despite only having a tiny change”
  1. Elijah NewrenJun 2, 2020
  2. Derrick StoleeJun 2, 2020
  3. Elijah NewrenJun 3, 2020
  4. Jonathan NiederJun 3, 2020
  5. Elijah NewrenJun 3, 2020
  6. Junio C HamanoJun 3, 2020

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.