From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Erik Schilling <erik.schilling@linaro.org>
Cc: tools@linux.kernel.org
Subject: Re: [BUG b4] encoding issues with single-patch series
Date: Thu, 22 Jun 2023 13:22:49 -0400 [thread overview]
Message-ID: <20230622-unafraid-dazzler-a413d5@meerkat> (raw)
In-Reply-To: <CTDYR84I395O.2UI69IKNO7B8A@fedora>
On Fri, Jun 16, 2023 at 11:22:51AM +0200, Erik Schilling wrote:
> Earlier, I sent a patch where I tried to CC Alex Bennée. The generated
> mail included the header:
>
> Content-Transfer-Encoding: 7bit
>
> the CC header got correctly escaped, but the mail body contained the CC
> with UTF-8 encoding:
>
> Cc: Alex Bennée <alex.bennee@linaro.org>
I was able to replicate this, thanks.
bugbot assign to me
-K
next prev parent reply other threads:[~2023-06-22 17:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-16 9:22 [BUG b4] encoding issues with single-patch series Erik Schilling
2023-06-16 16:53 ` Konstantin Ryabitsev
2023-06-16 16:55 ` Kernel.org Bugbot
2023-06-22 17:22 ` Konstantin Ryabitsev [this message]
2023-06-22 17:47 ` Kernel.org Bugbot
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=20230622-unafraid-dazzler-a413d5@meerkat \
--to=konstantin@linuxfoundation.org \
--cc=erik.schilling@linaro.org \
--cc=tools@linux.kernel.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