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

Re: [PATCH 0/3] send-pack: avoid resending unchanged objects after rebasing

From
Junio C Hamano <gitster@pobox.com>
Date
Oct 26, 2026, 17:26 UTC
Message-ID
<xmqq1p9cs79b.fsf@gitster.g>
In-Reply-To
<pull.2281.git.1793029565.gitgitgadget@gmail.com>
"Marc Strapetz via GitGitGadget" <gitgitgadget@gmail.com> writes:
Show 6 quoted lines
> A common feature-branch workflow is to push a branch, rebase it onto an
> updated upstream, and force-push the rewritten commits. Large blobs added or
> changed on the feature branch may survive the rebase unchanged. Although the
> receiver already has those blobs through the old branch tip, Git can pack
> and send them again. This can turn a small history rewrite into a large
> upload.

This sounds like the exact problem push negotiation was designed to address.

Previous: Marc Strapetz via GitGitGadgetNext: Marc Strapetz
Message 5 of 7 in “send-pack: avoid resending unchanged objects after rebasing”
  1. 0/3 send-pack: avoid resending unchanged objects after rebasingMarc Strapetz via GitGitGadget, Oct 26, 2026
  2. 1/3 t5516: record redundant blobs after rebasingMarc Strapetz via GitGitGadget, Oct 26, 2026
  3. 2/3 pack-objects: inspect selected haves for shared objectsMarc Strapetz via GitGitGadget, Oct 26, 2026
  4. 3/3 send-pack: avoid resending unchanged blobs after rebasingMarc Strapetz via GitGitGadget, Oct 26, 2026
  5. Junio C HamanoOct 26, 2026
  6. Marc StrapetzOct 26, 2026
  7. Marc StrapetzNov 4, 2026

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.