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.