From: Konstantin Ryabitsev <mricon@kernel.org>
To: users@kernel.org, tools@kernel.org
Subject: b4 v0.15.2 released
Date: Thu, 9 Apr 2026 15:03:15 -0400 [thread overview]
Message-ID: <20260409-daffy-maize-bettong-297fde@lemur> (raw)
Hi, all:
B4 v0.15.2 is now available with bug fixes for the review TUI and mbox
parsing. There won't be many more updates to the 0.15 stable branch, because
the master is diverging rapidly and backporting fixes is becoming challenging.
Upgrade using your usual mechanism:
pipx upgrade b4
New feature (introduced in response to a bugfix):
- review: show visual cue for patches unchanged between revisions --
when upgrading a series, identical patches now display a dim "≡"
marker so you can focus your review on patches that actually changed
Bug fixes:
- review: prevent double-sending of reviews carried over from a prior
revision after a series upgrade
- review: fix crash when stored message-id points to wrong version
thread after a series upgrade
- review: fix IndexError crash when toggling followups
- review: fix crash when background rescan completes while a modal
screen is active
- review: fix replies to additional patches being treated as inline
reviews on the wrong patch
- review: fix range-diff failing to find previous series revision
- review: fix upgrade branches polluting tracking DB with wrong
change-id
- review: show per-series error details after "Update all" instead of
only a total error count
- mbox: don't split on "---" in free-form reply messages (fixes body
content being silently discarded when encountering a "---" marker)
Thanks to Mark Brown and Miroslav Benes for the bug reports.
Best regards,
--
KR
reply other threads:[~2026-04-09 19:03 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=20260409-daffy-maize-bettong-297fde@lemur \
--to=mricon@kernel.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