From: Andrew Donnellan <ajd@linux.ibm.com>
To: Jeff King <peff@peff.net>, Jonathan Nieder <jrnieder@gmail.com>
Cc: patchwork@lists.ozlabs.org,
Stephen Rothwell <sfr@canb.auug.org.au>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Eric Blake <eblake@redhat.com>,
Christian Schoenebeck <qemu_oss@crudebyte.com>,
git@vger.kernel.org
Subject: Re: [PATCH] parser: Unmangle From: headers that have been mangled for DMARC purposes
Date: Fri, 11 Oct 2019 10:01:23 +1100 [thread overview]
Message-ID: <06541640-7eca-bc40-5c4b-9aa682d774a8@linux.ibm.com> (raw)
In-Reply-To: <20191010225405.GA19475@sigill.intra.peff.net>
On 11/10/19 9:54 am, Jeff King wrote:
> Neat. There was discussion on a similar issue recently in:
>
> https://public-inbox.org/git/305577c2-709a-b632-4056-6582771176ac@redhat.com/
>
> where a possible solution was to get senders to use in-body From
> headers even when sending their own patches.
I think that's a good idea.
>
> This might provide an alternate solution (or vice versa). I kind of like
> this one better in that it doesn't require the sender to do anything
> differently (but it may be less robust, as it assumes the receiver
> reliably de-mangling).
Yep, it's less robust - but OTOH there's always a long tail of users
stuck on old versions of git for whatever reason and having some logic
to detect DMARC munging may thus still be useful.
--
Andrew Donnellan OzLabs, ADL Canberra
ajd@linux.ibm.com IBM Australia Limited
next prev parent reply other threads:[~2019-10-10 23:01 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
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 [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=06541640-7eca-bc40-5c4b-9aa682d774a8@linux.ibm.com \
--to=ajd@linux.ibm.com \
--cc=alexandre.belloni@bootlin.com \
--cc=eblake@redhat.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=patchwork@lists.ozlabs.org \
--cc=peff@peff.net \
--cc=qemu_oss@crudebyte.com \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.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).