From: Joseph Myers <joseph@codesourcery.com>
To: Thomas Schwinge <thomas@codesourcery.com>
Cc: <gcc@gcc.gnu.org>
Subject: Re: Git commit "Author: [...] via Gcc-patches <gcc-patches@gcc.gnu.org>" (was: [gcc r11-5068] Update documentation for spec files)
Date: Tue, 17 Nov 2020 18:44:15 +0000 [thread overview]
Message-ID: <alpine.DEB.2.22.394.2011171841400.9088@digraph.polyomino.org.uk> (raw)
In-Reply-To: <87wnykbafw.fsf@euler.schwinge.homeip.net>
On Tue, 17 Nov 2020, Thomas Schwinge wrote:
> Should we have a Git commit hook to catch that (and similar variants)?
I've added a check for gcc-patches@gcc.gnu.org (or libstdc++@gcc.gnu.org
or fortran@gcc.gnu.org) as author email address in our commit_checker hook
(in ~gccadmin/hooks-bin). (Checking a few specific email addresses seems
a bit simpler than a more general rule of rejecting any @gcc.gnu.org
address that matches that of a mailing list other than
gccadmin@gcc.gnu.org.)
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2020-11-17 18:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201117001536.2429D386EC72@sourceware.org>
2020-11-17 9:26 ` Thomas Schwinge
2020-11-17 13:34 ` Jonathan Wakely
2020-11-17 14:25 ` Jeff Law
2020-11-17 18:44 ` Joseph Myers [this message]
2020-11-19 9:01 ` Git commit "Author: [...] via Gcc-patches <gcc-patches@gcc.gnu.org>" Florian Weimer
2020-11-21 20:19 ` Maciej W. Rozycki
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.22.394.2011171841400.9088@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gcc@gcc.gnu.org \
--cc=thomas@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).