From: "Daniel P. Berrangé" <berrange@redhat.com>
To: 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 11:30:19 +0000 [thread overview]
Message-ID: <YEYKy65zOHUWVu/D@redhat.com> (raw)
In-Reply-To: <CADPb22R89=EcWFcuFABZP3=L3CbUEq1eKPqNJY=SqDSoZ+CDnQ@mail.gmail.com>
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
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2021-03-08 11:31 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é [this message]
2021-03-08 16:05 ` Eric Blake
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=YEYKy65zOHUWVu/D@redhat.com \
--to=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 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.