From: Iain Sandoe <idsandoe@googlemail.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: Jason Merrill <jason@redhat.com>,
Jakub Jelinek <jakub@redhat.com>,
"Richard Earnshaw (lists)" <Richard.Earnshaw@arm.com>,
gcc@gcc.gnu.org, Joel Brobecker <brobecker@adacore.com>
Subject: Re: gcc-cvs mails for personal/vendor branches for merge commits
Date: Wed, 15 Jan 2020 17:57:00 -0000 [thread overview]
Message-ID: <89C87961-B21A-4E54-914F-40A89B5D5BBD@googlemail.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2001151628340.1765@digraph.polyomino.org.uk>
Joseph Myers <joseph@codesourcery.com> wrote:
> On Wed, 15 Jan 2020, Jason Merrill wrote:
>
>> On 1/15/20 9:56 AM, Joseph Myers wrote:
>>> On Wed, 15 Jan 2020, Jakub Jelinek wrote:
>>>
>>>> Or, if that is not possible, disable gcc-cvs mail for vendor and private
>>>> branches altogether?
>>
>> I think this is desirable. gcc-cvs should only mail about changes to master
>> and release branches.
>
> I thinks commit mails for changes to all branches are desirable (including
> refs/heads/devel/ branches, including user and vendor branches) - but they
> should only be for changes that are new to the repository. Existing
> practice in SVN was that all branches generated mails, we simply didn't
> have so many branches.
For user/vendor branches that are rebased (a desirable action), is there any
mechanism for excluding unchanged rebased commits from being seen as
“new�
I’m guessing that public development branches will probably gravitate to the
no non-FF mode, if they are to be used by people other than the primary author
.. although that does somewhat limit things; rebasing WIP onto trunk and
reorganising / squashing is useful as well.
Iain
next prev parent reply other threads:[~2020-01-15 16:38 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 [this message]
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
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=89C87961-B21A-4E54-914F-40A89B5D5BBD@googlemail.com \
--to=idsandoe@googlemail.com \
--cc=Richard.Earnshaw@arm.com \
--cc=brobecker@adacore.com \
--cc=gcc@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=jason@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).