From: Joel Brobecker <brobecker@adacore.com>
To: Iain Sandoe <iain@sandoe.co.uk>
Cc: Joseph Myers <joseph@codesourcery.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
"Richard Earnshaw (lists)" <richard.earnshaw@arm.com>
Subject: Re: limit on emails for merge commits.
Date: Fri, 17 Jan 2020 09:00:00 -0000 [thread overview]
Message-ID: <20200117083036.GD14671@adacore.com> (raw)
In-Reply-To: <56EBA2AB-EA82-4060-855F-6B052600F0A8@sandoe.co.uk>
Hi Ian,
> As I noted, 100 commits to master is a small number, so I expect this problem
> to fire almost every time someone does a merge of master to a devel or user
> branch (unless they have the habit of doing that almost daily, which I doubt
> for
> most).
The main goal of the limit is really to avoid accidents where someone
pushes something he shouldn't or something he didn't realize would
push so many commits. If the GCC repository is such that merges of
100 commits or more is going to be, if not routine, at least to be
expected, then perhaps increasing the limit would make sense.
What I would do is wait a bit and see. This may become moot soon,
depending on the direction that we want to take for vendor/user branches
with respect to emails. I'm still trying to think this over...
--
Joel
next prev parent reply other threads:[~2020-01-17 8:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-17 3:22 Iain Sandoe
2020-01-17 5:53 ` Joseph Myers
2020-01-17 8:17 ` Joel Brobecker
2020-01-17 8:29 ` Iain Sandoe
2020-01-17 9:00 ` Joel Brobecker [this message]
2020-01-17 14:32 ` Joseph Myers
2020-01-17 14:38 ` Richard Biener
2020-01-17 14:42 ` Joseph Myers
2020-01-17 16:47 ` Jason Merrill
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200117083036.GD14671@adacore.com \
--to=brobecker@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=iain@sandoe.co.uk \
--cc=joseph@codesourcery.com \
--cc=richard.earnshaw@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).