From: "Konstantin Ryabitsev" <konstantin@linuxfoundation.org>
To: tools@linux.kernel.org, users@linux.kernel.org
Subject: [b4] version 0.5.4 released (hotfix)
Date: Tue, 1 Dec 2020 11:29:46 -0500 [thread overview]
Message-ID: <20201201162946.44atowzr44m2yhky@chatter.i7.local> (raw)
[-- Attachment #1: Type: text/plain, Size: 373 bytes --]
Hi, all:
There was a nasty bug in 0.5.3 that caused "b4 ty" to wrongly match
every tracked series, so if you're using that functionality of b4 and
you're on version 0.5.3, you should upgrade to 0.5.4.
pip install --upgrade --user b4
If you are on version 0.5.2, you should be unaffected.
Thanks to Mark Brown and Martin K. Petersen for the report.
-K
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 235 bytes --]
reply other threads:[~2020-12-01 16:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20201201162946.44atowzr44m2yhky@chatter.i7.local \
--to=konstantin@linuxfoundation.org \
--cc=tools@linux.kernel.org \
--cc=users@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).