From: Joseph Myers <joseph@codesourcery.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Joel Brobecker <brobecker@adacore.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: Thu, 16 Jan 2020 22:03:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.21.2001161438440.18540@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20200116141147.GC10088@tucnak>
On Thu, 16 Jan 2020, Jakub Jelinek wrote:
> Couldn't it be then per-branch setting, whether to mail even commits
> that aren't new to the repository or not (like I understood it is already
> possible to decide per-branch whether to send mails at all)?
Feel free to add such suggestions to the issues at
<https://github.com/AdaCore/git-hooks/issues> (this one is
<https://github.com/AdaCore/git-hooks/issues/9>). Those issues are meant
to track all the cases where we think some changes to the hooks would be
useful for GCC (whether or not we've currently addressed them with local
changes to the hooks).
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2020-01-16 14:43 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 [this message]
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=alpine.DEB.2.21.2001161438440.18540@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=Richard.Earnshaw@arm.com \
--cc=brobecker@adacore.com \
--cc=gcc@gcc.gnu.org \
--cc=jakub@redhat.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).