Re: [PATCH v12 02/12] Iterate over the "refs/" namespace in for_each_[raw]ref
- From
Han-Wen Nienhuys <hanwen@google.com>
- Date
- May 11, 2020, 11:41 UTC
- Message-ID
- <CAFQ2z_OZ96xiVAM=kVX0KLXq1AinT=fxH1J=_6FOmO_2qvjncA@mail.gmail.com>
- In-Reply-To
- <xmqqh7wqxnns.fsf@gitster.c.googlers.com>
On Fri, May 8, 2020 at 8:54 PM Junio C Hamano <gitster@pobox.com> wrote:
Show 10 quoted lines
> > "Han-Wen Nienhuys via GitGitGadget" <gitgitgadget@gmail.com> writes: > > > From: Han-Wen Nienhuys <hanwen@google.com> > > > > This happens implicitly in the files/packed ref backend; making it > > explicit simplifies adding alternate ref storage backends, such as > > reftable. > > Makes sense.
It makes sense, but I'm not happy with this yet. I think the more consistent thing would be to have pseudo refs be integrated in the ref backend completely. Then, there could be a INCLUDE_PSEUDO_REFS flag that could be supplied to the iteration to decide whether or not to produce these refs.
-- 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