]> git.ipfire.org Git - thirdparty/git.git/commit - refs.c
bisect: consistently write BISECT_EXPECTED_REV via the refdb
authorPatrick Steinhardt <ps@pks.im>
Thu, 14 Dec 2023 13:37:13 +0000 (14:37 +0100)
committerJunio C Hamano <gitster@pobox.com>
Thu, 14 Dec 2023 17:25:27 +0000 (09:25 -0800)
commit0a06892ddde5bc3a82a4fe2963e3ea294252ffdd
treeafe9ab3282dac2c47c2c40f36123c7109a4177fa
parent70c70de616c306cd4bb7c70426e394d08f929dff
bisect: consistently write BISECT_EXPECTED_REV via the refdb

We're inconsistently writing BISECT_EXPECTED_REV both via the filesystem
and via the refdb, which violates the newly established rules for how
special refs must be treated. This works alright in practice with the
reffiles reference backend, but will cause bugs once we gain additional
backends.

Fix this issue and consistently write BISECT_EXPECTED_REV via the refdb
so that it is no longer a special ref.

Signed-off-by: Patrick Steinhardt <ps@pks.im>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
bisect.c
builtin/bisect.c
refs.c
t/t6030-bisect-porcelain.sh