archive mirror
 help / color / mirror / Atom feed
From: Konstantin Ryabitsev <>
Subject: b4-0.7 release next week
Date: Fri, 21 May 2021 17:44:53 -0400	[thread overview]
Message-ID: <20210521214453.rsslslzjarpeovl3@nitro.local> (raw)

Hi, all:

I will probably release b4-0.7.0 next week. The most notable change in it is a
(yet another) rewrite of patch attestation stuff, which mostly moved into its
own mini-library called "patatt". You can read about it in detail here:

or see its pypi page:

I hope this will be the last reimplementation, but I am leaving attestation
features marked as "EXPERIMENTAL" for another release round, until 0.8 when it
will move into beta. I intend to write a longer piece about patch attestation
in the near future, so I won't go into too much detail here.

If you're currently using "b4 attest" you should be able to continue doing so,
granted that you install the patatt dependency. If you're using b4 from git,

    git submodule update --init

If you are using b4 from pip, patatt will be pulled automatically in once 0.7
is out.

There's a few other notable changes:

- we've ditched Python's native "mbox" implementation since it's apparently
  incompatible with git's idea of "mbox" (see my mini-rant in this commit: ). We
  will now write git-compatible mbox files, or you can pass -M to write out
  maildirs (this can be made permanent with Maildirs
  are natively recognized by all git operations, so it's a perfectly good
  solution that avoids any possible mbox format ambiguities.

- b4 can now recognize partial rerolls, see example here:

- b4 will now accept mbox passed via stdin, so it's possible to pipe full 
  threads from mutt. See example here:

The master 0.7-dev branch should be stable enough at this point for day-to-day
operations, so if you're using b4 from a git checkout, you can switch to
master and give things a whirl. If you do, make sure you pull in the patatt
submodule via the command shown above.

If you find any regressions, please send them here.

Best regards,

                 reply	other threads:[~2021-05-21 21:44 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=20210521214453.rsslslzjarpeovl3@nitro.local \ \ \
    --subject='Re: b4-0.7 release next week' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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