| commit | 456333eb4d00a2bc8a71134bedfe5d3bc13a1932 | |
| author | Patrick Steinhardt <ps@pks.im> | |
| Thu, 18 Jan 2024 13:41:51 +0000 (18 14:41 +0100) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Thu, 18 Jan 2024 20:02:09 +0000 (18 12:02 -0800) | ||
| tree | 14c7941f3feb003c67fa3d269b51e3ae7124b42d | treesnapshot (tar.gz zip) |
| parent | 718a93ecc06ed59dda4e6a5d91b1c2169275694f | commitdiff |
reftable/stack: unconditionally reload stack after commit
After we have committed an addition to the reftable stack we call
`reftable_stack_reload()` to reload the stack and thus reflect the
changes that were just added. This function will only conditionally
reload the stack in case `stack_uptodate()` tells us that the stack
needs reloading. This check is wasteful though because we already know
that the stack needs reloading.
Call `reftable_stack_reload_maybe_reuse()` instead, which will
unconditionally reload the stack. This is merely a conceptual fix, the
code in question was not found to cause any problems in practice.
Signed-off-by: Patrick Steinhardt <ps@pks.im>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
After we have committed an addition to the reftable stack we call
`reftable_stack_reload()` to reload the stack and thus reflect the
changes that were just added. This function will only conditionally
reload the stack in case `stack_uptodate()` tells us that the stack
needs reloading. This check is wasteful though because we already know
that the stack needs reloading.
Call `reftable_stack_reload_maybe_reuse()` instead, which will
unconditionally reload the stack. This is merely a conceptual fix, the
code in question was not found to cause any problems in practice.
Signed-off-by: Patrick Steinhardt <ps@pks.im>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| reftable/stack.c | diffblobblamehistory |