Re: [PATCH 2/2] t5541: generalize reference locking
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Jan 11, 2024, 18:47 UTC
- Message-ID
- <xmqqa5pbhfkw.fsf@gitster.g>
- In-Reply-To
- <20240111072828.GD48154@coredump.intra.peff.net>
Jeff King <peff@peff.net> writes:
Show 11 quoted lines
> On Wed, Jan 10, 2024 at 06:52:30PM +0000, Justin Tobler via GitGitGadget wrote: > >> From: Justin Tobler <jltobler@gmail.com> >> >> Some tests set up reference locks by directly creating the lockfile. >> While this works for the files reference backend, reftable reference >> locks operate differently and are incompatible with this approach. >> Generalize reference locking by preparing a reference transaction. > > As with the first patch, I think we could use d/f conflicts to get the > same effect. Perhaps something like this:
Thanks for a great alternative. I agree that avoiding fifo indeed is a better way to go.