From: "Konstantin Ryabitsev" <konstantin@linuxfoundation.org>
To: Mark Brown <broonie@kernel.org>
Cc: tools@linux.kernel.org
Subject: Re: Exception from b4 ty
Date: Fri, 2 Oct 2020 21:17:12 -0400 [thread overview]
Message-ID: <20201003011712.vwigxq5pqp4d3gid@chatter.i7.local> (raw)
In-Reply-To: <20201002211248.GI5527@sirena.org.uk>
On Fri, Oct 02, 2020 at 10:12:48PM +0100, Mark Brown wrote:
> Hi,
>
> Attempting to generate thanks with b4 ty -a using current git master I
> get a traceback:
>
This is due to the earlier fix to set proper charsets. I need to
remember not to rely on Python's as_bytes() mechanism -- we get much
better control when we do as_string() and then do the encoding on our
own.
The latest master/stable-0.5.y has the fix for this, I hope -- plus for
the horrible header encoding.
-K
prev parent reply other threads:[~2020-10-03 1:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-02 21:12 Exception from b4 ty Mark Brown
2020-10-03 1:17 ` Konstantin Ryabitsev [this message]
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=20201003011712.vwigxq5pqp4d3gid@chatter.i7.local \
--to=konstantin@linuxfoundation.org \
--cc=broonie@kernel.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;
as well as URLs for NNTP newsgroup(s).