On Wed, Jul 14, 2021 at 3:07 AM Junio C Hamano <gitster@xxxxxxxxx> wrote: > [Stalled] > > * hn/reftable (2021-05-20) 27 commits I have some updates for the series pending, but I'm waiting for the preliminaries (test fixes, the errno stuff) to hit master. How do other folks deal with dependencies between topics? > * hn/refs-errno-cleanup (2021-07-07) 6 commits > - refs: make errno output explicit for refs_resolve_ref_unsafe > - refs: explicitly return failure_errno from parse_loose_ref_contents > - refs: add failure_errno to refs_read_raw_ref() signature > - refs: make errno output explicit for read_raw_ref_fn > - refs/files-backend: stop setting errno from lock_ref_oid_basic > - refs: remove EINVAL errno output from specification of read_raw_ref_fn > > Futz with the way 'errno' is relied on in the refs API to carry the > failure modes up the callchain. > > Expecting a (hopefully final) reroll. > cf. <CAFQ2z_NzykfcBSvtHQ10RZWxLP48+qArZk9HbDJQB4tNX-GtYA@xxxxxxxxxxxxxx> AEvar posted the corrected patch as part of his follow-up series. (https://public-inbox.org/git/patch-04.17-270cda29c3a-20210711T162803Z-avarab@xxxxxxxxx/). Would that work for you? -- Han-Wen Nienhuys - Google Munich I work 80%. Don't expect answers from me on Fridays. -- Google Germany GmbH, Erika-Mann-Strasse 33, 80636 Munich Registergericht und -nummer: Hamburg, HRB 86891 Sitz der Gesellschaft: Hamburg Geschäftsführer: Paul Manicle, Halimah DeLaine Prado
