From: Eric Blake <eblake@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>,
"Doug Evans" <dje@google.com>
Cc: Samuel Thibault <samuel.thibault@ens-lyon.org>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [PATCH] inet_parse: Clarify IPv6 comment and error message
Date: Mon, 8 Mar 2021 10:05:37 -0600 [thread overview]
Message-ID: <93eef612-08f6-7eb2-0d1b-de2ff0a58433@redhat.com> (raw)
In-Reply-To: <YEYKy65zOHUWVu/D@redhat.com>
On 3/8/21 5:30 AM, Daniel P. Berrangé wrote:
> On Sun, Mar 07, 2021 at 05:31:24PM -0800, Doug Evans wrote:
>> Not sure how this "Author email address is mangled" happened.
>>
>> $ git format-patch -o patches/error-parsing-ipv6 -1
>> $ git send-email --to='qemu-devel@nongnu.org,Samuel Thibault <
>> samuel.thibault@ens-lyon.org>,"Daniel P. Berrangé" <berrange@redhat.com>' \
>> --smtp-server=foo
>> patches/error-parsing-ipv6/0001-inet_parse-Clarify-IPv6-comment-and-error-message.patch
>>
>> It's possible my smtp-server arg munged things incorrectly, but I've done
>> the identical thing for previous patches and not seen this for at least
>> some of them.
>> Sigh.
>
> The 'via <qemu-devel@nongnu.org>' mangling is something that gnu.org
> mailman is configured to do. It used to do this in many scenarios, but
> supposedly it now only mangles when the sender has a bad DKIM signature
> and their domain has strict DMARC policies:
>
> https://lists.gnu.org/archive/html/qemu-devel/2019-09/msg00416.html
And the solution to avoid triggering the check failure is to include
'From: you <real@address>' as the first line of the body (which will
then override whatever header mangling the list inflicted on your
message). There are supposedly ways to configure git to do this
automatically for you as part of 'git send-email', but as I don't suffer
from the problem, I'm not sure off-hand what those steps are (git config
format.from ?)
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2021-03-08 16:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-08 0:29 [PATCH] inet_parse: Clarify IPv6 comment and error message Doug Evans via
2021-03-08 0:33 ` no-reply
2021-03-08 1:31 ` Doug Evans
2021-03-08 11:30 ` Daniel P. Berrangé
2021-03-08 16:05 ` Eric Blake [this message]
2021-03-08 11:31 ` 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=93eef612-08f6-7eb2-0d1b-de2ff0a58433@redhat.com \
--to=eblake@redhat.com \
--cc=berrange@redhat.com \
--cc=dje@google.com \
--cc=qemu-devel@nongnu.org \
--cc=samuel.thibault@ens-lyon.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).