From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: tools@linux.kernel.org
Cc: users@linux.kernel.org
Subject: b4 v0.11.0 available
Date: Mon, 19 Dec 2022 16:37:15 -0500 [thread overview]
Message-ID: <20221219213715.2qozw5emt5j7t3xr@nitro.local> (raw)
[-- Attachment #1: Type: text/plain, Size: 2477 bytes --]
Hello:
I am happy to announce b4 version 0.11.0. There are many enhancements to the
contributor workflow in this release, so everyone using "b4 prep" and related
features is encouraged to upgrade from 0.10.
# Major highlights
- b4 prep --compare-to N: shows a range-diff between your current prep branch
and the previously submitted revision N
- b4 ty: can be configured to always send mail without requiring the -S switch
(via setting b4.ty-send-mail=yes)
- b4 send will no longer send the entire series to the addresses found in
individual commit Cc: trailers; such addresses will only receive the cover
letter and the patches where they are explicitly Cc'd
- you can now set extra [PATCH] prefixes permanently either via b4 prep
--set-prefixes, via the cover letter subject line, or by using git's
format.subjectPrefix configuration
- b4 has internal changes to ensure that we generate 7-bit-clean headers for
all outgoing mail
- b4 send --reflect: prepares the patches but only sends them to yourself
- b4 prep --show-info: shows information about your prep-managed branch
# Documentation
Full documentation is available at:
https://b4.docs.kernel.org/en/stable-0.11.y/
# Upgrading
To upgrade to the latest version using pip:
pip install --upgrade b4
If you're using b4 from git, you can switch to the stable-0.11.y branch and
update the submodules.
# Acknowledgements
Special thanks to the following people who helped with this release, in
reverse-git order:
Luca Weiss <luca.weiss@fairphone.com>
Mark Brown <broonie@kernel.org>
Noralf Trønnes <noralf@tronnes.org>
Douglas Anderson <dianders@chromium.org>
Philippe Blain <levraiphilippeblain@gmail.com>
Maxime Ripard <maxime@cerno.tech>
Dmitry Torokhov <dmitry.torokhov@gmail.com>
Geert Uytterhoeven <geert@linux-m68k.org>
Quentin Schulz <quentin.schulz@theobroma-systems.com>
Rob Herring <robh@kernel.org>
Palmer Dabbelt <palmer@rivosinc.com>
Bjorn Helgaas <helgaas@kernel.org>
Nicolas Schier <n.schier@avm.de>
Neil Armstrong <neil.armstrong@linaro.org>
Peter Zijlstra <peterz@infradead.org>
Amjad Ouled-Ameur <aouledameur@baylibre.com>
Guillaume Ranquet <granquet@baylibre.com>
Leon Romanovsky <leon@kernel.org>
Great thanks for everyone who helped test-drive the new contributor-oriented
features despite a lot of potential for bugs.
-K
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next reply other threads:[~2022-12-19 21:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-19 21:37 Konstantin Ryabitsev [this message]
2022-12-20 20:40 ` b4 v0.11.0 available Peter Zijlstra
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=20221219213715.2qozw5emt5j7t3xr@nitro.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 read-only IMAP folder(s) and NNTP newsgroup(s).