summaryrefslogtreecommitdiff
path: root/t/t4013/diff.diff_initial..side
diff options
context:
space:
mode:
authorPatrick Steinhardt <ps@pks.im>2026-04-10 14:12:39 +0200
committerJunio C Hamano <gitster@pobox.com>2026-05-15 04:50:45 +0900
commit449650decf49b1fe5b1dac1c48dfb919e9b57b0d (patch)
treee2dce81e92c49e92fa8c8e24118dd0d0afd4b393 /t/t4013/diff.diff_initial..side
parent550d7b7c89a9cf80794c72e8c7d036164a5b1927 (diff)
oidtree: add ability to store data
The oidtree data structure is currently only used to store object IDs, without any associated data. So consequently, it can only really be used to track which object IDs exist, and we can use the tree structure to efficiently operate on OID prefixes. But there are valid use cases where we want to both: - Store object IDs in a sorted order. - Associated arbitrary data with them. Refactor the oidtree interface so that it allows us to store arbitrary payloads within the respective nodes. This will be used in the next commit. Signed-off-by: Patrick Steinhardt <ps@pks.im> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t4013/diff.diff_initial..side')
0 files changed, 0 insertions, 0 deletions