Marc Strapetz describes a common workflow: push a feature branch, rebase it onto updated upstream, and force-push. Large blobs that survive the rebase unchanged can be packed and sent again even though the receiver already has them through the old branch tip. The result can be a large upload for a small history rewrite.
The three-patch series makes send-pack pass locally available old tips of forced non-fast-forward branch updates as haves_to_inspect. It does this only for refs selected for sending, and skips fast-forward and rejected updates. It also skips shallow repositories, whose thin-pack pushes already inspect negative tips with --objects-edge-aggressive.
Pack-objects gains an --inspect-have <commit> input line. It compares the root trees of those commits with the outgoing tips using the existing sparse tree marking, without walking the commits' histories. The tests expect two packed objects, the rebased commit and its tree, instead of three.
Junio C Hamano's response was brief: this sounds like the exact problem push negotiation was designed to address.
Strapetz replied that the series is meant to optimize Git's default packing for forced updates without adding a negotiation phase. He said it avoids the extra exchanges of push.negotiate and the broader recursive tree marking of --objects-edge-aggressive. Whether that scope convinces reviewers is not yet shown in the thread.