From: "Konstantin Ryabitsev" <konstantin@linuxfoundation.org>
To: users@linux.kernel.org, tools@linux.kernel.org
Subject: [b4] version 0.6.1 is available
Date: Mon, 7 Dec 2020 16:42:12 -0500 [thread overview]
Message-ID: <20201207214212.qyehpt6o6nxfuzz4@chatter.i7.local> (raw)
[-- Attachment #1: Type: text/plain, Size: 2050 bytes --]
Hi, all:
This is a new major release of b4. Version 0.6.0 contained a crasher for
when dkimpy was not installed and therefore we're going straight to
0.6.1.
The following highlights the most important changes as compared to
version 0.5:
- Extended trailer format recognition for follow-up trailers, e.g.:
Reviewed-by: Dev Eloper <dev@eloper.com>
[for some_foo_function in bar.c]
- Add support for local maildirs, allowing to grab threads straight from
a local maildir or mailbox, e.g.:
b4 am -m ~/Mail <some-msgid>
(don't try this on huge mailboxes, though, as there is no support for
intelligent header search -- b4 will iterate ALL messages looking for
the thread you need).
- Preserve trailer order by default instead of sorting them. If you
like your trailers sorted, define the order in the config file; see
b4(5) for configuration file details.
- Perform DKIM verification on all patches and messages containing
follow-up trailers. To turn off, set b4.attestation-check-dkim=no in
gitconfig. To work, DKIM attestation required dkimpy and dnspython
libraries; if not found, DKIM checks will not be performed.
- Reimplement developer patch attestation using in-header hashes instead
of detached certification documents. For more info on the proposal,
see:
https://git.kernel.org/pub/scm/linux/kernel/git/mricon/patch-attestation-poc.git/plain/README.rst
To set up PGP attestation for your patches, see README.rst. It's free!
- A handful of fixes and improvements, many already backported to 0.5.y.
If you installed from pip, you can upgrade using:
pip install --user --upgrade b4
This will pull in dkimpy and dnspython dependencies.
Special thanks to everyone who contributed to this version, not just
from shortlog below, but also for bug reports and functionality
suggestions.
$ git shortlog -s v0.5.0..
80 Konstantin Ryabitsev
3 Kyle Meyer
1 Marc Zyngier
4 Philippe Blain
2 Tudor Ambarus
Best regards,
-K
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 235 bytes --]
reply other threads:[~2020-12-07 21:42 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=20201207214212.qyehpt6o6nxfuzz4@chatter.i7.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 NNTP newsgroup(s).