From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: tools@linux.kernel.org, users@linux.kernel.org
Subject: b4 0.12.3 available
Date: Fri, 23 Jun 2023 14:10:49 -0400 [thread overview]
Message-ID: <20230623-display-prevalent-44c89b@meerkat> (raw)
[-- Attachment #1: Type: text/plain, Size: 2612 bytes --]
Hello:
I am pleased to announce b4 version 0.12.3, which includes many bugfixes and
minor feature improvements. Everyone must upgrade.
To upgrade using pip:
pip install --upgrade b4
If you're using a git checkout, you can just update to the latest
stable-0.12.y HEAD.
$ git shortlog v0.12.2..v0.12.3
Dominique Martinet (1):
b4.sh: keep existing PYTHONPATH if set
Erik Schilling (1):
docs: fix smtpServerPort option
Ira Weiny (1):
b4: Allow prep new branch while on a b4 managed branch
Konstantin Ryabitsev (17):
Up version to 0.12.3-dev
ez-trailers: don't crash when there are no follow-ups received
ez: do not trust local commands to properly reflect
Add subscribe/unsubscribe to badtrailers
ez: better fix for "no follow-up trailers" condition
Consider '@' safe in msgid URLs
Clean headers before adding them to the pre-scissors email
Fix to properly handle under-scissors patches with a unixfrom line
ez: only include base-branch when using non-default strategy
ez: make message-ids use today's date
ez: make it easier to send single-patch series
Fix wrong CTR header after 8bit cover content is mixed in
trailers: normalize address after parsing
shazam: switch to top of git tree before running git-am
Properly quote the address before adding into From
ez: store sent prefixes with the tag message
Up release to 0.12.3
Matthieu Baerts (2):
trailers: accept recognized link trailers
trailers: add 'Closes' as recognized link trailer
Maxime Ripard (1):
b4: Fix envelopeSender handling
Philippe Blain (2):
mbox.py::make_am: simplify check for early return
am, shazam: allow cherry-picking an out-of-series patch
Rob Herring (1):
ez: Fix 'trailers -F' used on a single commit
Special thanks to the following people who helped with this release (in
reverse-log order):
Erik Schilling <erik.schilling@linaro.org>
Josselin Poiret <dev@jpoiret.xyz>
Andrew Cooper <andrew.cooper3@citrix.com>
Mark Brown <broonie@kernel.org>
Christian Brauner <brauner@kernel.org>
Maxime Ripard <mripard@kernel.org>
Philippe Blain <levraiphilippeblain@gmail.com>
Rob Herring <robh@kernel.org>
Dominique Martinet <asmadeus@codewreck.org>
Ira Weiny <ira.weiny@intel.com>
Nick Desaulniers <ndesaulniers@google.com>
Matthieu Baerts <matthieu.baerts@tessares.net>
Best wishes,
-K
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
reply other threads:[~2023-06-23 18:10 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=20230623-display-prevalent-44c89b@meerkat \
--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).