Karthik Nayak f1dcdd6deb reftable: pick either 'oid' or 'target' for new updates ...

When creating a reference transaction update, we can provide the old/new
oid/target for the update. We have checks in place to ensure that for
each old/new, either oid or target is set and not both.

In the reftable backend, when dealing with updates without the
`REF_NO_DEREF` flag, we don't selectively propagate data as needed.
Since there are no active users of the path, this is not caught. As we
want to introduce the 'symref-update' command in the upcoming commit,
which would use this flow, correct it.

Helped-by: Patrick Steinhardt <ps@pks.im>
Signed-off-by: Karthik Nayak <karthik.188@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>

2024-06-07 10:25:45 -07:00

..

debug.c

refs: remove create_symref and associated dead code

2024-05-07 08:51:50 -07:00

files-backend.c

refs: specify error for regular refs with old_target

2024-06-07 10:25:44 -07:00

iterator.c

refs: always treat iterators as ordered

2024-02-21 09:58:06 -08:00

packed-backend.c

refs: remove create_symref and associated dead code

2024-05-07 08:51:50 -07:00

packed-backend.h

Revert "Merge branch 'ps/avoid-unnecessary-hook-invocation-with-packed-refs'"

2022-04-13 15:51:33 -07:00

ref-cache.c

refs: always treat iterators as ordered

2024-02-21 09:58:06 -08:00

ref-cache.h

hash-ll.h: split out of hash.h to remove dependency on repository.h

2023-04-24 12:47:32 -07:00

refs-internal.h

refs: create and use ref_update_expects_existing_old_ref()

2024-06-07 10:25:44 -07:00

reftable-backend.c

reftable: pick either 'oid' or 'target' for new updates

2024-06-07 10:25:45 -07:00