Re: [PATCH v2 02/13] reftable: define the public API
- From
Han-Wen Nienhuys <hanwen@google.com>
- Date
- Oct 10, 2020, 17:03 UTC
- Message-ID
- <CAFQ2z_PVVGHi_N1uw7A4xUczm9WPkpXkQ9Yte9gCNO9ExAupyw@mail.gmail.com>
- In-Reply-To
- <20201009211300.GA2774782@google.com>
On Fri, Oct 9, 2020 at 11:13 PM Emily Shaffer <emilyshaffer@google.com> wrote:
Show 7 quoted lines
> Of course, taking a completed project - like your initial reftable > submission - and then chopping it up into a cute story of commits is a > pain in the ***. Doing it twice - or more - is just aggravating. So I > wonder whether we can bikeshed what story would look nice before you > even pick up your 'git rebase -i'? Doing that bikeshedding here on list > means that we also have a chance for someone to interrupt and say, "no, > that organization doesn't make sense" - or even for someone to say
It would be great if you could bikeshed about this while I'm on holiday :)
That said, I think it's worthwhile to first look at the commit that uses the library to implement a ref backend, because that will show better how the reftable library fits with the way that Git likes to consume its data.
-- 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