On Tue, Feb 06, 2024 at 02:10:41PM -0800, Karthik Nayak wrote: > Junio C Hamano <gitster@xxxxxxxxx> writes: > > Junio C Hamano <gitster@xxxxxxxxx> writes: > >> Phillip Wood <phillip.wood123@xxxxxxxxx> writes: [snip] > > For now, let's block the kn/for-all-refs topic until we figure out > > the UI issue. Which means this (and the reftable integration that > > started to depend on it) will not be in the upcoming release. > > > > I think it makes sense to remove the kn/for-all-refs topic for now. > > I also think that the reftable integration branch can go forward though, > since the difference between v2 and v3 of that series was simply that > v3 was rebased on top of kn/for-all-refs. So we can continue using v2. I've sent a rebased v4 that evicted the kn/for-all-refs dependency. This also allowed me to adapt to some fixes for the reftable library which have been merged down to `master` now so that the corresponding tests are now with `test_expect_success`. Patrick
Attachment:
signature.asc
Description: PGP signature
