From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Florian Weimer <fw@deneb.enyo.de>
Cc: Thomas Schwinge <thomas@codesourcery.com>, gcc@gcc.gnu.org
Subject: Re: Git commit "Author: [...] via Gcc-patches <gcc-patches@gcc.gnu.org>"
Date: Sat, 21 Nov 2020 20:19:14 +0000 (GMT) [thread overview]
Message-ID: <alpine.LFD.2.21.2011212011360.656242@eddie.linux-mips.org> (raw)
In-Reply-To: <87r1opra7v.fsf@mid.deneb.enyo.de>
On Thu, 19 Nov 2020, Florian Weimer wrote:
> > Should we have a Git commit hook to catch that (and similar variants)?
>
> It's also possible to move to a mailing list host which does not
> rewrite the From: header. The commit hook is better than nothing,
> although it's probably a bit tricky—some of use sourceware.org
> addresses, and “ via ” could appear in a name.
I keep wondering what they do for vger.kernel.org mailing lists and the
LKML in particular that we can't to avoid `From:' header rewriting. Our
patch volume is nothing to theirs, which is probably why we can cope most
of the time (I use my outbox to apply my own patches for example), though
they do partially avoid the issue by relying more on GIT pulls than we do.
Maciej
prev parent reply other threads:[~2020-11-21 20:19 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 ` Git commit "Author: [...] via Gcc-patches <gcc-patches@gcc.gnu.org>" (was: [gcc r11-5068] Update documentation for spec files) Thomas Schwinge
2020-11-17 13:34 ` Jonathan Wakely
2020-11-17 14:25 ` Jeff Law
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 [this message]
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.LFD.2.21.2011212011360.656242@eddie.linux-mips.org \
--to=macro@linux-mips.org \
--cc=fw@deneb.enyo.de \
--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).