From: "Konstantin Ryabitsev" <konstantin@linuxfoundation.org>
To: Mark Brown <broonie@kernel.org>
Cc: tools@linux.kernel.org
Subject: Re: b4 ty unicode crash
Date: Mon, 28 Dec 2020 13:18:30 -0500 [thread overview]
Message-ID: <20201228181830.wi726giciurlhunh@chatter.i7.local> (raw)
In-Reply-To: <20201228161347.GD5352@sirena.org.uk>
[-- Attachment #1: Type: text/plain, Size: 543 bytes --]
On Mon, Dec 28, 2020 at 04:13:47PM +0000, Mark Brown wrote:
> Hi,
>
> When I run b4 ty and it finds what looks like:
>
> https://lore.kernel.org/r/ec66399502514edbb1de3cf9bff08b1d@realtek.com
>
> I get a traceback:
I have an attempted fix for this in master/stable-0.6.y, but it will only
apply to future series you fetch with "b4 am", not any existing tracking files
in ~/.local/share/b4. It's not a perfect fix, since the underlying Python bug
is still there, but the changes should avoid hitting it in most cases.
-K
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 235 bytes --]
next prev parent reply other threads:[~2020-12-28 18:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-28 16:13 b4 ty unicode crash Mark Brown
2020-12-28 16:56 ` Konstantin Ryabitsev
2020-12-28 18:18 ` Konstantin Ryabitsev [this message]
2020-12-29 12:16 ` [tools] " Mark Brown
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=20201228181830.wi726giciurlhunh@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).