From: Jason Merrill <jason@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>,
Iain Sandoe <idsandoe@googlemail.com>
Cc: Joseph Myers <joseph@codesourcery.com>,
Jakub Jelinek <jakub@redhat.com>,
"Richard Earnshaw (lists)" <Richard.Earnshaw@arm.com>,
gcc@gcc.gnu.org
Subject: Re: gcc-cvs mails for personal/vendor branches for merge commits
Date: Fri, 17 Jan 2020 19:15:00 -0000 [thread overview]
Message-ID: <d8e47384-3f53-c9ac-6306-14ac7a396a71@redhat.com> (raw)
In-Reply-To: <20200117165552.GG4164@adacore.com>
On 1/17/20 11:55 AM, Joel Brobecker wrote:
>> AFAIU, we have access to more fine-grained information; isn’t it possible
>> to differentiate “new” commits, from ‘merges’ and from ‘rebases’?
>> (because a ‘new’ commit does not have the extra fields set up for merges
>> and rebases).
>
> In my opinion, this would create a lot of complication for the benefits
> being gained. I also think that the more variations of behaviors you
> introduce, the harder is becomes for people to know what's right and
> what's not expected. People then start getting surprised and start
> asking about it. At best, it's just a quick answer, but in some cases,
> it takes time to remember why we set things up the way they are and why
> it doesn't make sense to change it. Over the years, I have really learnt
> to enjoy the benefits of consistency, even if it is means some areas
> are suboptimal. The "suboptimality" can still be a better compromise
> overall than a superengineered system.
Spamming the list with emails every time someone merges master to their
development branch sounds highly suboptimal, and likely to lead to
disabling email entirely for those branches. Is it so complicated to
send a single email for a merge commit or non-fast-forward push?
Jason
next prev parent reply other threads:[~2020-01-17 17:22 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-15 15:07 Jakub Jelinek
2020-01-15 15:42 ` Joseph Myers
2020-01-15 15:51 ` Jakub Jelinek
2020-01-15 16:01 ` Joseph Myers
2020-01-15 16:42 ` Jason Merrill
2020-01-15 16:58 ` Joseph Myers
2020-01-15 17:09 ` Jason Merrill
2020-01-15 17:57 ` Iain Sandoe
2020-01-15 20:20 ` Jason Merrill
2020-01-19 14:10 ` Segher Boessenkool
2020-01-19 22:40 ` Julien "_FrnchFrgg_" Rivaud
2020-01-20 18:42 ` Segher Boessenkool
2020-01-15 19:21 ` Richard Earnshaw (lists)
2020-01-16 9:55 ` Joseph Myers
2020-01-16 14:28 ` Joel Brobecker
2020-01-16 14:35 ` Jakub Jelinek
2020-01-16 14:43 ` Richard Earnshaw (lists)
2020-01-16 18:51 ` Jakub Jelinek
2020-01-16 22:03 ` Joseph Myers
2020-01-16 18:58 ` Joseph Myers
2020-01-17 16:47 ` Joel Brobecker
2020-01-17 17:22 ` Iain Sandoe
2020-01-17 17:59 ` Joel Brobecker
2020-01-17 19:15 ` Jason Merrill [this message]
2020-01-17 22:39 ` Joel Brobecker
2020-01-18 9:50 ` Iain Sandoe
2020-01-18 11:07 ` Jason Merrill
2020-01-18 14:30 ` Joseph Myers
2020-01-17 17:23 ` Joseph Myers
2020-01-17 21:14 ` Joel Brobecker
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=d8e47384-3f53-c9ac-6306-14ac7a396a71@redhat.com \
--to=jason@redhat.com \
--cc=Richard.Earnshaw@arm.com \
--cc=brobecker@adacore.com \
--cc=gcc@gcc.gnu.org \
--cc=idsandoe@googlemail.com \
--cc=jakub@redhat.com \
--cc=joseph@codesourcery.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).