archive mirror
 help / color / mirror / Atom feed
From: Konstantin Ryabitsev <>
Subject: b4 v0.12.0 available
Date: Fri, 20 Jan 2023 11:57:12 -0500	[thread overview]
Message-ID: <20230120165712.rznwonw6nbfhc7fo@meerkat.local> (raw)

[-- Attachment #1: Type: text/plain, Size: 2353 bytes --]


I am happy to announce b4 v0.12.0. The primary purpose of this release is to
work around critical bugs discovered in the Python email.message module that
was causing message corruption when certain conditions were met. Specifically,
we have discovered and reported the following Python bugs:


None of them are fixed at this time, and even if they are, we're still looking
at months or years before everyone uses Python versions that do not contain

For this reason, b4 v0.12 implements its own message generation routines that
sidesteps the problem entirely. Since patches are ultimately very simple
plaintext messages without any mime content, this wasn't too challenging to
implement, but there are probably subtle bugs hiding in that code as well.
But, at least we can fix those when they are reported.

Everyone using "b4 send" really should upgrade to 0.12.

# Other features in 0.12

The primary focus was fixing Python's email bugs, so the list of other
features is small:

## b4 mbox --refetch <mboxfile>

Since version 0.11, "b4 am" saves messages with minimal headers. If you would
like to respond to messages in a saved mbox file as part of your review
process, you can restore all original headers using:

    b4 mbox --refetch that.mbox

## Always hiding To/Cc trailers in the cover letters

B4 uses the cover letter to track To/Cc addressees. In version 0.12, "b4 send"
always hides them from generated cover letters, so they don't overwhelm
reviewers (this info is already in the headers anyway).

## Bugfixes

Mostly minor bugfixes and corner-case crashers.

# Upgrading

To upgrade from pip:

    pip install --upgrade b4

# Thanks

The following people helped with this release, in reverse-git-log order:

    Geert Uytterhoeven <>
    Vishal Verma <>
    Rob Herring <>
    Matthieu Baerts <>
    Thomas Weißschuh <>
    Nathan Chancellor <>
    Mark Brown <>
    Quentin Schulz <>


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

                 reply	other threads:[~2023-01-20 16:57 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230120165712.rznwonw6nbfhc7fo@meerkat.local \ \ \ \

* 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).