From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: tools@kernel.org, users@kernel.org
Subject: b4 0.13.0 available
Date: Thu, 15 Feb 2024 14:17:47 -0500 [thread overview]
Message-ID: <20240215-refreshing-spotted-kiwi-ae2e99@lemur> (raw)
Hello, all:
I am happy to announce the release of b4-0.13.0. There are no major new
features that were introduced since 0.12, but there are enough feature updates
to warrant a "Quality of Life" point-release.
# Updating
If you installed via pip, you can upgrade using:
pip install --upgrade b4
If you're using b4 via the git checkout, you can either update to latest
master, or checkout the new stable-0.13.y branch. You can also download signed
tarballs from the usual location:
https://kernel.org/pub/software/devel/b4/
# Notable changes
Besides the usual bugfixes, some of which have been backported to 0.12.y
already:
## am, shazam
- `b4 am` now has a `--single-message` flag that lets you process a single
message and ignore any other parts of a thread; this is useful when there is
a patch series sent as attachments to a single message
- `--apply-cover-trailers` is now the default behaviour
- when patchwork integration is configured, `b4 am` will attempt to retrieve
the CI status of patches
## prep, send
- `b4 prep --show-info` can do a lot more now, including showing information
about branches that aren't currently checked out
- `b4 prep` gained a --cleanup option to properly archive and remove old
b4-prep-managed branches
- `b4 send` has a `--preview-to` option that lets you send a pre-review of your
series to your colleagues, mentors, or bosses
- various fixes and improvements to `b4 send` functionality
## Other notable changes
- b4 can now take config options on commandline, allowing to override global
configs via scripted invocations
- improvements to `b4 diff` that should make it work more reliably for series
without exact object matches
# Special thanks
As usual, thank you to the following people who all helped with the release
(in the reverse-changelog order):
- Philippe Blain
- Marcos Paulo de Souza
- Nikolay Borisov
- Miquel Raynal
- Lucas De Marchi
- Nicolas Schier
- Steven Rostedt
- Mark Brown
- Dan Williams
- Ira Weiny
- Mario Limonciello
- Jani Nikula
- Leonard Göhrs
- Geert Uytterhoeven
- Andrew Cooper
- Joel Granados
- Duje Mihanović
- Erik Schilling
- Josselin Poiret
- Christian Brauner
- Maxime Ripard
- Palmer Dabbelt
- Conor Dooley
- Rob Herring
- Dominique Martinet
- Matthieu Baerts
- Nick Desaulniers
- Michael Ellerman
- Alyssa Ross
- Alison Schofield
- Marc Kleine-Budde
That's quite an impressively long list!
Best regards,
-K
reply other threads:[~2024-02-15 19:17 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=20240215-refreshing-spotted-kiwi-ae2e99@lemur \
--to=konstantin@linuxfoundation.org \
--cc=tools@kernel.org \
--cc=users@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 read-only IMAP folder(s) and NNTP newsgroup(s).