From: Peter Maydell <peter.maydell@linaro.org>
To: eblake@redhat.com
Cc: qemu-devel@nongnu.org, Andrey Drobyshev <andrey.drobyshev@virtuozzo.com>
Subject: Re: [PATCH] maint: Tweak comment in mailmap to sound friendlier
Date: Wed, 27 Sep 2023 10:21:53 +0100 [thread overview]
Message-ID: <CAFEAcA8zf4odT13FJF=MgSnCiZnRYDF5PDuL40CMe0KPh3kTNw@mail.gmail.com> (raw)
In-Reply-To: <20230926203946.3303600-2-eblake@redhat.com>
On Tue, 26 Sept 2023 at 21:41, <eblake@redhat.com> wrote:
>
> From: Eric Blake <eblake@redhat.com>
>
> Documenting that we should not add new lines to work around SPF
> rewrites sounds foreboding; the intent is instead that new lines here
> are okay, but indicate a second problem elsewhere in our build process
> that we should also consider fixing at the same time, to keep the
> section from growing without bounds.
>
> Mentioning DMARC alongside SPF may also help people grep for this
> scenario, as well as documenting the 'git config' workaround that can
> be used by submitters to avoid the munging issue in the first place.
>
> Fixes: 3bd2608d ("maint: Add .mailmap entries for patches claiming list authorship")
> CC: Andrey Drobyshev <andrey.drobyshev@virtuozzo.com>
> Cc: Peter Maydell <peter.maydell@linaro.org>
> Signed-off-by: Eric Blake <eblake@redhat.com>
> ---
>
> I'm sending this email with a temporary 'git config sendemail.from
> eblake@redhat.com', to see if the added advice actually adds the extra
> line. It did not show up in my editor window, though, so this patch
> may need further tweaking to get the instructions right. Since I
> don't normally suffer from SPF/DMARC munging, I may not be the best
> person to test the right workaround. Or maybe 'git config' does not
> yet have the right workaround already available as a turnkey solution
> we can suggest.
Well, the From: line appeared in my copy of the email, so I guess it works.
Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
thanks
-- PMM
next prev parent reply other threads:[~2023-09-27 9:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-26 20:39 [PATCH] maint: Tweak comment in mailmap to sound friendlier eblake
2023-09-27 9:21 ` Peter Maydell [this message]
2023-09-27 10:34 ` Andrey Drobyshev
2023-09-27 14:06 ` Eric Blake
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='CAFEAcA8zf4odT13FJF=MgSnCiZnRYDF5PDuL40CMe0KPh3kTNw@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=andrey.drobyshev@virtuozzo.com \
--cc=eblake@redhat.com \
--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).