From: Andrew Donnellan <ajd@linux.ibm.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: patchwork@lists.ozlabs.org,
Stephen Rothwell <sfr@canb.auug.org.au>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
git@vger.kernel.org
Subject: Re: [PATCH] parser: Unmangle From: headers that have been mangled for DMARC purposes
Date: Fri, 11 Oct 2019 08:13:01 +1100 [thread overview]
Message-ID: <236b9c32-b501-79a7-8366-26d64ceac24f@linux.ibm.com> (raw)
In-Reply-To: <20191010194132.GA191800@google.com>
On 11/10/19 6:41 am, Jonathan Nieder wrote:
> Interesting! I'm cc-ing the Git mailing list in case "git am" might
> wnat to learn the same support.
Argh, that reminds me... this patch only rewrites the name and email
that is recorded as the Patchwork submitter, it doesn't actually rewrite
the From: header when you fetch the mbox off Patchwork.
Part of me would really like to keep Patchwork mboxes as close as
possible to the mbox we ingested, but on the other hand it means the
mangled address is still going to land in the git repo at the end... so
I should probably just change it?
--
Andrew Donnellan OzLabs, ADL Canberra
ajd@linux.ibm.com IBM Australia Limited
next prev parent reply other threads:[~2019-10-10 21:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20191010062047.21549-1-ajd@linux.ibm.com>
2019-10-10 19:41 ` [PATCH] parser: Unmangle From: headers that have been mangled for DMARC purposes Jonathan Nieder
2019-10-10 21:13 ` Andrew Donnellan [this message]
2019-10-10 23:16 ` Daniel Axtens
2019-10-10 23:40 ` Stephen Rothwell
2019-10-10 22:54 ` Jeff King
2019-10-10 23:01 ` Andrew Donnellan
2019-10-10 23:06 ` Jeff King
2019-10-11 15:42 ` Daniel Axtens
2019-10-11 15:51 ` Jeff King
2019-10-13 11:05 ` Andrew Donnellan
2019-10-11 4:29 ` Junio C Hamano
2019-10-11 4:36 ` Andrew Donnellan
2019-10-11 4:50 ` Andrew Donnellan
2019-10-11 13:13 ` Christian Schoenebeck
2019-10-11 17:36 ` Ian Kelling
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=236b9c32-b501-79a7-8366-26d64ceac24f@linux.ibm.com \
--to=ajd@linux.ibm.com \
--cc=alexandre.belloni@bootlin.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=patchwork@lists.ozlabs.org \
--cc=sfr@canb.auug.org.au \
/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 NNTP newsgroup(s).