From: Tobias Geerinckx-Rice via "Development of GNU Guix and the GNU System distribution." <guix-devel@gnu.org>
To: Ryan Prior <rprior@protonmail.com>,
Ryan Prior via Guix-patches <guix-patches@gnu.org>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>, 45644@debbugs.gnu.org
Subject: Re: [bug#45644] closed (Re: [bug#45644] [PATCH] gnu: esbuild: Update to 0.8.29.)
Date: Mon, 04 Jan 2021 18:02:54 +0100 [thread overview]
Message-ID: <8735zgmy81.fsf@nckx> (raw)
In-Reply-To: <hS2msVZbjH7OQ2Wf9J-kjO6hbTvnv7kKCJsCu8Me0ezSE1UoNHQqm07DkBrT7lXabBtD4LYSr2hR2M1Di7bcDgBitJKr9rgM2VAxFdcAyKc=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 2227 bytes --]
via,
Ryan Prior via Guix-patches via 写道:
> git send-email --to=guix-patches@gnu.org --suppress-cc=self
> 0001-gnu-esbuild-Update-to-0.8.29.patch
I (and many others) use git send-email, so it can't be directly to
blame. I've never used it with an explicit patch file like that,
though, only ‘-<n>’, but that should change little.
You shouldn't bother too much with Mailgun & the like, this has
nothing to do with Protonmail.
> So I have to imagine that either Protonmail or your email server
> are changing the email address.
Looks like us. It's by design. Mailing lists *have to* change
email addresses now. If gnu.org sent out mail to mi^Whundreds of
Guix users claiming to be directly from you:
From: Ryan Prior <rprior@protonmail.com>
it would amount to a poor forgery in this age of DMARC & DKIM.
We'd be spamholed into oblivion by every recipient who doesn't go
through extra (manual/heuristic) trouble to whitelist known MLs.
And rightly so.
So instead we munge the From header[0], with a note to make
receivers aware of that fact:
From: Ryan Prior via Guix-patches via <guix-patches@gnu.org>
Resent-From: Ryan Prior <rprior@protonmail.com>
But this happens to every mail we resend, not only yours:
From: Leo Famulari <leo@xxx>
Resent-From: Leo Famulari <leo@xxx>
I can't say what went wrong, only that I routinely apply patches
from Guix MLs through mu4e and ‘git am’ without trouble. I think.
The last ~dozen patches signed off by me seem fine, at least.
Leo, does this happen to any guix-patch@ or just Ryan's?
> I don't know if it's possible with the commit-signing system you
> have in place to rewrite Guix repo history, or whether it would
> be worth it,
No and no. Sorry.
We also can't use .mailmap to rewrite the user-facing address.
We'd be mapping all of guix-patches@gnu.org to you.
I can't think of a way to fix the past. It's unfortunate, but
we'll live.
Kind regards,
T G-R
[0]: We (Mailman?) get this part wrong, however: ‘Fu Barian via
<beep@gnu.boop>’ looks cute, but it abuses the format & clutters
address books everywhere with the bogus name ‘Fu Barian via’.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2021-01-04 17:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <X/J1vu/GBTP9DKhH@jasmine.lan>
[not found] ` <20210104014732.19791-1-rprior@protonmail.com>
[not found] ` <handler.45644.D45644.160972538318518.notifdone@debbugs.gnu.org>
2021-01-04 2:47 ` [bug#45644] closed (Re: [bug#45644] [PATCH] gnu: esbuild: Update to 0.8.29.) Ryan Prior via Guix-patches via
2021-01-04 17:02 ` Tobias Geerinckx-Rice via Development of GNU Guix and the GNU System distribution. [this message]
2021-01-04 17:07 ` Tobias Geerinckx-Rice via Development of GNU Guix and the GNU System distribution.
2021-01-04 17:56 ` Leo Famulari
2021-01-05 5:01 ` Mailman From header rewrite (was: [bug#45644] closed (Re: [bug#45644] [PATCH] gnu: esbuild: Update to 0.8.29.)) Kyle Meyer
2021-01-05 5:22 ` Kyle Meyer
2021-01-05 5:35 ` Ryan Prior via Development of GNU Guix and the GNU System distribution.
2021-07-18 5:44 ` Mailman From header rewrite Sarah Morgensen
2021-07-24 22:00 ` Kyle Meyer
2022-10-29 21:13 ` Kyle Meyer
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8735zgmy81.fsf@nckx \
--to=guix-devel@gnu.org \
--cc=45644@debbugs.gnu.org \
--cc=guix-patches@gnu.org \
--cc=me@tobias.gr \
--cc=rprior@protonmail.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).