From: Andrew Donnellan <ajd@linux.ibm.com>
To: Jeff King <peff@peff.net>, Daniel Axtens <dja@axtens.net>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Christian Schoenebeck <qemu_oss@crudebyte.com>,
patchwork@lists.ozlabs.org, Eric Blake <eblake@redhat.com>,
git@vger.kernel.org
Subject: Re: [PATCH] parser: Unmangle From: headers that have been mangled for DMARC purposes
Date: Sun, 13 Oct 2019 22:05:49 +1100 [thread overview]
Message-ID: <a59c318f-476b-c3ab-fa6b-5067503820a3@linux.ibm.com> (raw)
In-Reply-To: <20191011155151.GA19395@sigill.intra.peff.net>
On 12/10/19 2:51 am, Jeff King wrote:
> On Sat, Oct 12, 2019 at 02:42:49AM +1100, Daniel Axtens wrote:
>
>>>> where a possible solution was to get senders to use in-body From
>>>> headers even when sending their own patches.
>> [...]
>> I'm not sure this solution is correct.
>>
>> If I take a patch from Andrew, backport it, and send to the list, Andrew
>> will be listed in the in-body From. However, he shouldn't be the sender
>> from the Patchwork point of view: he shouldn't get the patch status
>> notification emails - I should. We don't want to spam an original author
>> if their patch is backported to several different releases, or picked up
>> and resent in someone else's series, etc etc. So unless I've
>> misunderstood something, we can't rely on the in-body from matching
>> Patchwork's understanding of the sender.
>
> Yeah, it may be that patchwork and git have two different priorities
> here. From my perspective, the problem is getting the patch into a git
> repo with the right author name. But patchwork may want to make the
> distinction between author and sender.
>
Yes, I was referring to the git am case, not the Patchwork case.
--
Andrew Donnellan OzLabs, ADL Canberra
ajd@linux.ibm.com IBM Australia Limited
next prev parent reply other threads:[~2019-10-13 11:06 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
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 [this message]
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=a59c318f-476b-c3ab-fa6b-5067503820a3@linux.ibm.com \
--to=ajd@linux.ibm.com \
--cc=alexandre.belloni@bootlin.com \
--cc=dja@axtens.net \
--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.
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).