From: "Konstantin Ryabitsev" <konstantin@linuxfoundation.org>
To: tools@linux.kernel.org
Cc: users@linux.kernel.org
Subject: b4 v0.3.4 released
Date: Mon, 23 Mar 2020 18:20:41 -0400 [thread overview]
Message-ID: <20200323222041.uzfcexg2wy74jqdd@chatter.i7.local> (raw)
[-- Attachment #1: Type: text/plain, Size: 810 bytes --]
Hello:
I pushed v0.3.4 to pypi, so if you're using it from there, you can run
"pip install --user --upgrade b4" to grab the latest version.
Notable changes compared to 0.3.3:
- deals properly with series versions that are only mentioned in the
cover letter
- adds a b4.sh wrapper that lets you run b4 without needing to install
with pip
- fixes a couple of backtraces due to bugs with patch attestation
- adds a caching layer to avoid hitting lore.kernel.org on repeating
runs (e.g. when rerunning with -t, -s, -l, and similar)
- properly refuses to install on python version < 3.5
- uses more descriptive filenames for "b4 am" mboxes
Thanks to the following people for their feedback:
- Geoff Levand
- Mark Brown
- Kees Cook
- Geert Uytterhoeven
- James Bottomley
-K
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 235 bytes --]
next reply other threads:[~2020-03-23 22:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-23 22:20 Konstantin Ryabitsev [this message]
2020-03-25 2:11 ` [kernel.org users] b4 v0.3.4 released Jason A. Donenfeld
2020-03-25 2:19 ` Jason A. Donenfeld
2020-03-25 15:05 ` Konstantin Ryabitsev
2020-03-25 15:26 ` Konstantin Ryabitsev
2020-03-26 16:04 ` Rob Herring
2020-03-26 16:11 ` Rob Herring
2020-03-26 16:16 ` Konstantin Ryabitsev
2020-03-26 16:27 ` James Bottomley
2020-03-26 16:31 ` Geert Uytterhoeven
[not found] ` <15FFE6D3B979AF4C.32445@linux.kernel.org>
2020-03-26 16:32 ` Konstantin Ryabitsev
2020-03-26 20:18 ` Jason A. Donenfeld
2020-03-27 18:15 ` Konstantin Ryabitsev
2020-04-06 21:53 ` Konstantin Ryabitsev
2020-09-22 22:17 ` Rob Herring
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=20200323222041.uzfcexg2wy74jqdd@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).