From: Eric Blake <eblake@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>, qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [Qemu-devel] [PATCH] scripts: report on author emails that are mangled by the mailing list
Date: Thu, 23 Aug 2018 09:07:27 -0500 [thread overview]
Message-ID: <684bc04e-0e25-cd9b-b773-1b5b140586d3@redhat.com> (raw)
In-Reply-To: <20180823102502.28122-1-berrange@redhat.com>
On 08/23/2018 05:25 AM, Daniel P. Berrangé wrote:
> In some cases the Author: email address in patches submitted to the
> list gets mangled such that it says
>
> John Doe via Qemu-devel <qemu-devel@nongnu.org>
>
> This change is a result of workarounds for DMARC policies.
>
> Subsystem maintainers accepting patches need to catch these and fix
> them before sending pull requests, so a checkpatch.pl test is highly
> desirable.
>
> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
> ---
> scripts/checkpatch.pl | 4 ++++
> 1 file changed, 4 insertions(+)
>
Adding it here will let patchew flag such message; the workaround is for
the submitter to resubmit with an explicit 'From: User Name
<address@example.com>' line in the body of the email.
Reviewed-by: Eric Blake <eblake@redhat.com>
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2018-08-23 14:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-23 10:25 [Qemu-devel] [PATCH] scripts: report on author emails that are mangled by the mailing list Daniel P. Berrangé
2018-08-23 10:33 ` Cornelia Huck
2018-08-23 10:41 ` Peter Maydell
2018-08-23 10:59 ` Daniel P. Berrangé
2018-08-23 16:18 ` Markus Armbruster
2018-08-23 14:07 ` Eric Blake [this message]
2018-10-19 11:22 ` Daniel P. Berrangé
2018-10-19 12:00 ` Paolo Bonzini
2018-10-19 12:13 ` Daniel P. Berrangé
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=684bc04e-0e25-cd9b-b773-1b5b140586d3@redhat.com \
--to=eblake@redhat.com \
--cc=berrange@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/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).