On Sat, Feb 03, 2024 at 12:41:01PM -0800, Junio C Hamano wrote: > Patrick Steinhardt <ps@xxxxxx> writes: > > > this is the second version of my patch series that introduces the > > reftable backend. > > > > This version addresses the feedback by Karthik. I don't think it really > > makes sense to spell out every change here -- the range diff should > > likely be easier to digest. > > This, when merged to 'seen' (which also has "for-each-ref now thinks > an empty string is a signal to show ref-like things outside the > refs/ hierarchy" topic, kn/for-all-refs), seems to break *-reftable > CI tests, cf. https://github.com/git/git/actions/runs/7765401528 > > I'll tentatively eject the topic from 'seen', even though I have a > suspicion that it byitself would pass all the tests. > > Thanks. Yup, this is known due to the semantic conflict with kn/for-all-refs, as you point out. Karthik already sent a single-line change in this thread that fixes the issue. I'll rebase the patch series tomorrow and pull in the topic as a dependency and adapt accordingly. Thanks! Patrick
Attachment:
signature.asc
Description: PGP signature
