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

[PATCH 0/4] send-pack: introduce a `no-ref-delta` capability

From
Taylor Blau <ttaylorr@openai.com>
Date
Jul 13, 2026, 01:11 UTC
Message-ID
<alQ7U8TOWjhasaWk@com-79390>

This series teaches 'send-pack' to avoid writing `REF_DELTA` entries when the receiving end asks it to.

Some 'receive-pack' implementations may wish to retain the incoming pack without first building an object ID index, in which case requiring delta bases to appear earlier in the same pack makes them easier to locate.

The new `no-ref-delta` capability is deliberately independent of `ofs-delta`, and thus asking the sender not to write `REF_DELTA` entries does not by itself mean that the receiver understands `OFS_DELTA` entries. The corresponding `pack-objects` option therefore controls `REF_DELTA` without changing whether `OFS_DELTA` is allowed.

The main complication is reuse. Ordinary delta reuse reuses the compressed delta instructions, but rewrites the entry header and base reference. It can therefore write an existing `REF_DELTA` as an `OFS_DELTA` when `--delta-base-offset` is in effect and the base has already been written in the output pack. Deltas against preferred or external thin-pack bases cannot be reused in this way, since those bases do not appear in the output at all.

Bitmap pack reuse is different, since it copies entries directly from an existing pack. Under `--no-ref-delta`, it must inspect candidate objects individually, omit `REF_DELTA` entries from direct pack reuse, and leave them to the normal object-writing path.

The patches are organized as follows:
 - The first patch teaches 'test-tool pack-deltas' to list each delta's
   representation and base. I originally wrote the series without this,
   but found that writing tests demonstrating which specific *kind* of
   delta representation was chosen to be awkward without having a
   dedicated test helper.
 - The second patch introduces the `--no-ref-delta` option in
   'pack-objects', though initially with delta- and bitmap-reuse
   disabled for the sake of simplicity.
 - The third patch re-enables ordinary delta- and bitmap-reuse where it
   is safe to do so.
 - The final patch advertises and consumes the new `no-ref-delta`
   capability.
Thanks in advance for your review!
Taylor Blau (4):
  t/helper: teach pack-deltas to list delta entries
  pack-objects: introduce `--no-ref-delta`
  pack-objects: support reuse with `--no-ref-delta`
  send-pack: honor `no-ref-delta` capability
 Documentation/git-pack-objects.adoc         |  8 ++-
 Documentation/gitprotocol-capabilities.adoc | 17 ++++-
 builtin/pack-objects.c                      | 29 ++++++--
 builtin/receive-pack.c                      |  5 ++
 pack-bitmap.c                               | 30 +++++---
 pack-bitmap.h                               |  3 +-
 send-pack.c                                 |  4 ++
 send-pack.h                                 |  1 +
 t/helper/test-pack-deltas.c                 | 69 ++++++++++++++++++
 t/t5300-pack-object.sh                      | 79 ++++++++++++++++++++-
 t/t5332-multi-pack-reuse.sh                 | 16 +++++
 t/t5516-fetch-push.sh                       | 14 ++++
 12 files changed, 252 insertions(+), 23 deletions(-)
-- 
2.55.0
Next: Taylor Blau
Message 1 of 7 in “send-pack: introduce a `no-ref-delta` capability”
  1. 0/4 send-pack: introduce a `no-ref-delta` capabilityTaylor Blau, Jul 13, 2026
  2. Taylor BlauJul 13, 2026
  3. Jeff KingJul 14, 2026
  4. Taylor BlauJul 14, 2026
  5. Jeff KingJul 18, 2026
  6. Taylor BlauJul 18, 2026
  7. Jeff KingJul 20, 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.