From: Markus Armbruster <armbru@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Daniel P. Berrangé" <berrange@redhat.com>,
"QEMU Developers" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] scripts: report on author emails that are mangled by the mailing list
Date: Thu, 23 Aug 2018 18:18:55 +0200 [thread overview]
Message-ID: <878t4xcaz4.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <CAFEAcA-jfnWjAA3zhUKZ2ZBJdD+JmndLgrigJnxuVFJN5e=pXg@mail.gmail.com> (Peter Maydell's message of "Thu, 23 Aug 2018 11:41:20 +0100")
Peter Maydell <peter.maydell@linaro.org> writes:
> On 23 August 2018 at 11:25, Daniel P. Berrangé <berrange@redhat.com> 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.
>
> I do wonder if overall we'd be better off with the other
> workaround (don't change From lines in list emails, don't
> add "[Qemu-devel]" prefix to subject lines)... It would be
> a one-off annoyance to people who filter list mail on subject
> rather than other headers, but it would get rid of this annoying
> wart where a handful of senders end up with their mail with
> a from address that our patch management tools don't handle
> very well...
Mangling e-mail headers is a bad idea. The fact that it's commonly held
only makes it worse.
If you can hack QEMU, filtering on List-Id should not be an
insurmountable obstacle.
next prev parent reply other threads:[~2018-08-23 16:19 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 [this message]
2018-08-23 14:07 ` Eric Blake
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=878t4xcaz4.fsf@dusky.pond.sub.org \
--to=armbru@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.