Re: What's cooking in git.git (Jan 2022, #05; Wed, 19)

From: Han-Wen Nienhuys <hanwen@google.com>
Date: Jan 20, 2022, 11:03 UTC
Message-ID: <CAFQ2z_NZL+8No44863K5n7cQkHmtn35_BtKKTQiFzHweHfTHag@mail.gmail.com>
In-Reply-To: <CAPc5daVFUoK1UQUO5jdsLSUQ8XfkiEk+MoWKg2CZB0=N6N9XXg@mail.gmail.com>

On Thu, Jan 20, 2022 at 11:44 AM Junio C Hamano <gitster@pobox.com> wrote:

Show 13 quoted lines

>
> > > * hn/reftable-coverity-fixes (2021-12-22) 18 commits
> > >  - reftable: be more paranoid about 0-length memcpy calls
> > >  - reftable: add print functions to the record types
> > ..
> > >  Expecting a reroll.
> >
> > The reroll was sent on Jan 12. I dropped the "reftable: be more
> > paranoid about 0-length memcpy calls" from the series.
>
> The last time you mentioned "Jan 12", I went back to the lore archive
> for the original thread [1] and didn't find anything but a few comment
> messages on that day.

Sorry, you're right. I didn't understand your previous message on the subject.

GGG has started enforcing line wrapping commit messages at 60-76 chars (https://github.com/git/git/pull/1152#issuecomment-1011290837). I hadn't realized it didn't send out the series.

I grepped for '76' in Documentation/*, but couldn't find any note. Is this new requirement for GGG documented somewhere?

-- 
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