From: "Konstantin Ryabitsev" <konstantin@linuxfoundation.org>
To: tools@linux.kernel.org, users@linux.kernel.org
Subject: [b4] version 0.5.3 is available
Date: Wed, 25 Nov 2020 17:15:22 -0500 [thread overview]
Message-ID: <20201125221522.jk4kdfyfur6zblvp@chatter.i7.local> (raw)
[-- Attachment #1: Type: text/plain, Size: 1301 bytes --]
Hi, all:
I've released b4 version 0.5.3, which offers a handful of bugfixes and
small enhancements in the stable-0.5.y branch. This is expected to be
the last release in the 0.5.x series.
Notable changes:
- properly grab cover letters that don't have a diffstat
- require that trailers are at least 2 chars long
- improve "b4 ty" on cherry-picked series
- fix some crashers
If you installed using pip, you should be able to upgrade using the
following command:
pip install --upgrade --user b4
Full shortlog is below.
Konstantin Ryabitsev (13):
Cover letters may not have a diffstat
Require that a trailer is at least 2 chars long
Set charset in order to generate MIME headers
Use bytes when dumping to stdout
Don't crash when no valid patches are found
Fix some cherry-picking corner cases
Fix header encoding introduced by earlier fix
Fix crasher when attempting a 3-way prep
Unquote msgid if we're getting a full https URL
Improve ty with cherrypicked subsets
Fix crash on incomplete series thanks tracking
Fix thanks-tracking of partial series
Increment version to 0.5.3 in prep for release
Marc Zyngier (1):
Fix handling of series with the [PATCHvX] defect
-K
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 235 bytes --]
next reply other threads:[~2020-11-25 22:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-25 22:15 Konstantin Ryabitsev [this message]
2020-11-26 9:58 ` [kernel.org users] [b4] version 0.5.3 is available Jiri Slaby
2020-11-26 13:56 ` Konstantin Ryabitsev
2020-11-26 14:26 ` Jason A. Donenfeld
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=20201125221522.jk4kdfyfur6zblvp@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).