From: Jeff Law <law@redhat.com>
To: Thomas Schwinge <thomas@codesourcery.com>, 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 07:25:46 -0700 [thread overview]
Message-ID: <36e32efb-0152-6b4e-acfa-77db3f4feb39@redhat.com> (raw)
In-Reply-To: <87wnykbafw.fsf@euler.schwinge.homeip.net>
On 11/17/20 2:26 AM, Thomas Schwinge wrote:
> Hi!
>
> (As discussed before...), in 2020, email doesn't work anymore the way it
> did years ago... ;-/ (Let's please *not* discuss this here.)
>
> So we're now dealing with emails with "From: [...] via Gcc-patches
> <gcc-patches@gcc.gnu.org>", etc.
>
> ... which occasionally then ends up in Git commit author:
>
> On 2020-11-17T00:15:36+0000, Jeff Law via Gcc-cvs <gcc-cvs@gcc.gnu.org> wrote:
>> https://gcc.gnu.org/g:a019766f996f57e53a8d1a9e72033e1e1487a150
>>
>> commit r11-5068-ga019766f996f57e53a8d1a9e72033e1e1487a150
>> Author: Armin Brauns via Gcc-patches <gcc-patches@gcc.gnu.org>
> Should we have a Git commit hook to catch that (and similar variants)?
>
>
> (This is not to blame Jeff, of course; it's very easy to not notice
> that.)
Yea. I keep having to remember which header to pull the author from. I
strongly suspected one or more had slipped through.
jeff
next prev parent reply other threads:[~2020-11-17 14:25 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 [this message]
2020-11-17 18:44 ` Joseph Myers
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=36e32efb-0152-6b4e-acfa-77db3f4feb39@redhat.com \
--to=law@redhat.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).