From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: tools@linux.kernel.org, users@linux.kernel.org
Subject: b4-0.9.0 available
Date: Fri, 17 Jun 2022 15:01:53 -0400 [thread overview]
Message-ID: <20220617190153.tvi5lkzlvemeqou5@meerkat.local> (raw)
[-- Attachment #1: Type: text/plain, Size: 3177 bytes --]
Hello:
After a bit of a hiatus, I am finally able to work on b4 again, so here's
version 0.9.0 that implements one major new feature and adds some other
improvements to existing features.
# new: b4 shazam
This command is very similar to "b4 am", but it allows you to apply patches
directly to the git repository without the need pipe the output of "b4 am" to
"git am".
The shazam command has three modes of operation:
1. default mode that applies patches directly to your git repository, just
like passing the .mbox file to git-am
2. with -H, shazam will try to prepare the patch series into FETCH_HEAD, which
can then be checked out into a branch or merged with git-merge. This
effectively makes patch series work similar to pull requests.
3. with -M, shazam will do the same as with -H, but will also exec git-merge
with the cover letter prepared as part of the merge commit message. You can
see it in action here: https://asciinema.org/a/502421
Please trial it out and report any problems or improvements you would like to
see.
# improved: --no-parent mode for b4 am/shazam
Per popular request, you are now able to break threads at the message-id
specified using the --no-parent flag to am/shazam subcommands. In this case,
b4 should ignore any parent messages in the thread and only operate on the
message itself and any of its descendants. This should help unconfuse b4 when
someone submits an auxiliary patch in the middle of a thread and you want to
be able to get *just* that patch and not the parent series.
# improved: send mail with b4 ty -S
If you're using b4 ty, you can use the -S switch to have b4 send mail directly
instead of just writing .thanks files. Additionally, b4 ty gained --dry-run to
help make sure that things are looking good before you actually send mail.
# improved: mailmap support for b4 ty
If you're using b4 ty, it will now properly check the .mailmap file when
creating reply messages. You can also exclude entire domains from ever being
included in to/cc when generating thank-you replies using the email-exclude
setting, e.g.:
[b4]
email-exclude = *@codeaurora.org
In addition to the above, there are fixes and improvements to many aspects of
b4.
# Upgrading
To upgrade from pip, run:
pip install --upgrade b4
Alternatively, wait for distros to pick up the new release.
If you want to run b4 from your git checkout, check the README that documents
this option.
# Thanks
Thank you for your patience while I was unable to dedicate a lot of time to
b4. I had to spend a lot of time migrating and upgrading hardware at LF, and
then a certain dictator started a bloody invasion in Ukraine, which
significantly affected my ability to concentrate on most other things. If you
can, please support Ukraine's fight against the invading fascist regime
through your preferred humanitarian org.
I would also like to thank the following people who helped with this release,
in the reverse git log order:
- David Vernet <void@manifault.com>
- Mark Brown <broonie@kernel.org>
- Rob Herring <robh@kernel.org>
- Jens Axboe <axboe@kernel.dk>
- Kees Cook <keescook@chromium.org>
Best regards,
Konstantin
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next reply other threads:[~2022-06-17 19:01 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 19:01 Konstantin Ryabitsev [this message]
2022-06-20 8:40 ` b4-0.9.0 available Geert Uytterhoeven
2022-06-21 23:38 ` Linus Walleij
2022-06-22 5:49 ` Vinod Koul
2022-06-21 15:20 ` Geert Uytterhoeven
2022-06-21 15:29 ` Konstantin Ryabitsev
2022-06-21 15:41 ` Geert Uytterhoeven
2022-06-21 15:55 ` Linus Torvalds
2022-06-21 16:03 ` Jason A. Donenfeld
2022-06-21 16:59 ` Konstantin Ryabitsev
2022-06-21 17:49 ` Jason A. Donenfeld
2022-06-21 18:29 ` Konstantin Ryabitsev
2022-06-21 18:45 ` Jason A. Donenfeld
2022-06-21 19:27 ` Konstantin Ryabitsev
2022-06-21 19:42 ` Jason A. Donenfeld
2022-06-21 19:43 ` Geert Uytterhoeven
2022-06-21 19:50 ` Jason A. Donenfeld
2022-06-21 20:06 ` Konstantin Ryabitsev
2022-06-21 20:29 ` Jason A. Donenfeld
2022-06-21 21:25 ` Bjorn Andersson
2022-06-23 23:33 ` Theodore Ts'o
2022-06-24 13:51 ` Jason Gunthorpe
2022-06-24 15:29 ` Theodore Ts'o
2022-06-24 15:34 ` Mark Brown
2022-06-24 16:05 ` Theodore Ts'o
2022-06-24 15:52 ` Konstantin Ryabitsev
2022-06-24 16:05 ` James Bottomley
2022-06-24 16:16 ` Konstantin Ryabitsev
2022-06-24 16:29 ` James Bottomley
2022-06-24 16:06 ` Jason Gunthorpe
2022-06-24 16:16 ` Mark Brown
2022-06-24 17:51 ` Chuck Lever
2022-06-24 8:34 ` Nicolas Ferre
2022-06-21 15:53 ` Jason A. Donenfeld
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=20220617190153.tvi5lkzlvemeqou5@meerkat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.