Re: Question about git: merging to gccgo branch

[Ian Lance Taylor <iant at golang dot org>]

On Wed, Jan 22, 2020 at 10:39 AM Joseph Myers <joseph@codesourcery.com> wrote:
>
> On Wed, 22 Jan 2020, Ian Lance Taylor wrote:
>
> > I don't want to send 581 e-mails.  I would be happy not sending any
> > e-mails at all.  I would also be happy sending 1 e-mail.
>
> This is the issue we've discussed in
> <https://github.com/AdaCore/git-hooks/issues/9> and the messages linked
> from there.
>
> Until we have a proper fix not to send emails for the commits being
> merged, I've increased that limit to 1000 for GCC, as it doesn't seem
> useful to make people split the commits merged into batches of at most
> 100.  I've also disabled the check for the default commit message for
> merge commits, since it seems that wasn't being useful in practice for
> branches where merges are appropriate and a separate check prevents merge
> commits on master and release branches.

Thanks.  Should I go ahead and commit and generate 581 e-mail
messages, or should I wait?  In order to keep up with the Go release
cycle I'd like to commit this merge soon if possible.

Ian