All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mark Brown" <broonie@kernel.org>
To: tools@linux.kernel.org, konstantin@linuxfoundation.org
Subject: Re: [tools] b4 ty unicode crash
Date: Tue, 29 Dec 2020 12:16:46 +0000	[thread overview]
Message-ID: <20201229121646.GA4786@sirena.org.uk> (raw)
In-Reply-To: <20201228181830.wi726giciurlhunh@chatter.i7.local>

[-- Attachment #1: Type: text/plain, Size: 448 bytes --]

On Mon, Dec 28, 2020 at 01:18:30PM -0500, Konstantin Ryabitsev wrote:

> 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.

Great, thanks!  I'll let you know if I run into anything.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 499 bytes --]

      reply	other threads:[~2020-12-29 12:17 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
2020-12-29 12:16   ` Mark Brown [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=20201229121646.GA4786@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=konstantin@linuxfoundation.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 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.