Re: What's cooking in git.git (Aug 2026, #05)
Junio C Hamano <[email protected]>
| Newsgroups | org.kernel.vger.git |
|---|---|
| Message-ID | <[email protected]> |
Patrick Steinhardt <[email protected]> writes: >> * tb/send-pack-no-ref-delta (2026-07-12) 4 commits >> - send-pack: honor `no-ref-delta` capability >> - pack-objects: support reuse with `--no-ref-delta` >> - pack-objects: introduce `--no-ref-delta` >> - t/helper: teach pack-deltas to list delta entries >> >> 'git send-pack' has been taught to refrain from sending 'REF_DELTA' >> encoded packfiles when the other side asks it to. >> >> Needs review. >> source: <alQ7WKITYDXfiVn9@com-79390> > > In <an0EkMZGEbg6LERc@com-79390> we've agreed that this series can be > evicted for now in favor of > <[email protected]>, as Taylor > still needs some more time to rethink the approach in there. > >> * tb/midx-incremental-custom-base (2026-06-12) 3 commits >> - midx-write: include packs above custom incremental base >> - midx: pass custom '--base' through incremental writes >> - t5334: expose shared `nth_line()` helper >> >> The 'git multi-pack-index write --incremental' command has been >> corrected to properly honor the '--base' option. Previously, the >> custom base was ignored by the normal write path; packs from layers >> above the selected base were incorrectly skipped by the pack exclusion >> logic, and reachability closure for bitmaps was broken. >> >> Needs review. >> source: <[email protected]> > > I'll try to have a look at this series later today. Thanks.