From: "Konstantin Ryabitsev" <konstantin@linuxfoundation.org>
To: users@linux.kernel.org, tools@linux.kernel.org
Subject: b4 v0.4.0 available with new features
Date: Fri, 24 Apr 2020 13:04:42 -0400 [thread overview]
Message-ID: <20200424170442.ad3b3j5f5vkbcmvb@chatter.i7.local> (raw)
[-- Attachment #1: Type: text/plain, Size: 3647 bytes --]
Hi, all:
I am happy to release b4 version 0.4.0 that contains a set of
improvements and new features. To upgrade from pypi, run:
pip install --upgrade --user b4
Or you can clone the repository directly:
git clone https://git.kernel.org/pub/scm/utils/b4/b4.git -b stable-0.4.y b4
You can run ./b4.sh from the repository or set an alias/symlink to that
wrapper.
# Improvements
- When a series is missing patches, b4 is now able to backfill them from
other mailing lists tracked on lore.kernel.org. This feature will be
improved when public-inbox is able to collect a thread from across all
sources.
- If both patch and metadata are identical between rerolls (v1 -> v2),
b4 will automatically carry over trailers from v1 to v2. This is handy
if there is an sob on [PATCH v2 7/15] from a maintainer that is
missing from an identical [PATCH v3 7/15]. In my observation, this
happens very rarely, though.
- Many bugfixes that were also backported into stable-0.3.y.
# New features
## b4 pr
You can now process pull requests in addition to patch series:
b4 pr <msgid>
- downloads that message
- parses the pull request
- checks that the remote tip is where the message says it should be
- makes sure the base-commit is present in the tree
- makes sure the tip commit isn't already in one of the branches
- checks if FETCH_HEAD already is at that commit
- if the above two checks pass, performs a git fetch
- runs pgp verify checks on FETCH_HEAD and shows the results
b4 pr --check <msgid>
Runs all of the checks above, but doesn't perform the actual fetch.
Useful if you don't remember if you've already processed a pull
request or not.
b4 pr --explode <msgid>
Runs basic sanity checks and then:
- performs a git fetch
- runs a "git format-patch" for base-commit..FETCH_HEAD
- adds the same to/from/cc headers as in the pull request
- properly threads each patch below the pull request
- saves that into a <msgid>.mbox file
The above is handy if you want to comment on something in a pull
request and not have to hunt around for sender/cc information.
b4 pr --help
- will show you more information about subcommands available
## b4 ty
Allows you to automate a lot of "thanks, applied" and "thanks, merged"
feedback for series and pull requests that were fetched with "b4 am" and
"b4 pr".
b4 ty --help
- will show you information about subcommands available
### For patch series:
- find all commits in the current branch that were made by you
(committer=user.email)
- see if any of them match patch-id's or patch titles tracked from
previous "b4 am" runs
- create an automatic reply message with the summary of the commit and
save it as a .thanks file in the output directory provided
### For pull requests
- Match the tip commit in the pull request to your current branch
- create an automatic reply message with the summary of the merge and
save it as a .thanks file in the output directory provided
### Sending .thanks files
We do not currently automatically send the .thanks files, though this
functionality will be added in the future for the cases where we find a
[sendemail] section in .gitconfig.
For the moment, you can send these using "git send-email", "sendmail",
or you can use bsync or other tools to automatically upload them to the
Drafts folder of your mail service provider.
# Acknowledgements
I would like to thank Mark Brown for being a willing guinea pig for
trying out the "b4 ty" feature.
-K
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 235 bytes --]
next reply other threads:[~2020-04-24 17:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-24 17:04 Konstantin Ryabitsev [this message]
2020-04-24 23:35 ` [tools] b4 v0.4.0 available with new features Martin K. Petersen
2020-04-27 18:40 ` Konstantin Ryabitsev
2020-04-28 2:12 ` Martin K. Petersen
2020-04-28 15:16 ` Konstantin Ryabitsev
2020-04-29 3:25 ` Martin K. Petersen
2020-04-28 16:03 ` [kernel.org users] " Jason Gunthorpe
2020-05-04 17:09 ` [kernel.org users] " Rob Herring
2020-05-04 17:17 ` Jason Gunthorpe
2020-05-04 20:09 ` Konstantin Ryabitsev
2020-05-04 23:07 ` Jason Gunthorpe
2020-05-04 20:03 ` Konstantin Ryabitsev
2020-05-04 22:58 ` Jason Gunthorpe
2020-05-04 23:04 ` Rob Herring
2020-05-06 19:23 ` Rob Herring
2020-05-07 20:20 ` Konstantin Ryabitsev
2020-05-12 19:07 ` Rob Herring
2020-06-09 22:24 ` Rob Herring
2020-07-27 14:52 ` Konstantin Ryabitsev
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=20200424170442.ad3b3j5f5vkbcmvb@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).