From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: users@linux.kernel.org, tools@linux.kernel.org
Subject: b4 v0.8.0 is available
Date: Wed, 1 Sep 2021 10:16:37 -0400 [thread overview]
Message-ID: <20210901141637.fmvgs4hnk6m4ym7x@meerkat.local> (raw)
Hello, all:
A new version of b4 is available that adds functionality to better work with
newer public-inbox features available on lore.kernel.org. There aren't many
new features compared to version 0.7.y, but everyone is encouraged to upgrade.
If you installed from pypi, just do:
pip install --upgrade b4
If you're using b4 straight from a checkout, you can switch to branch-0.8.y
and run "git submodule update" to pull in the latest patatt updates.
Other than lore.kernel.org compatibility changes, the only significant
difference with version 0.7.3 is the --guess-base code, which should be a lot
more useful with this release. E.g. this message back from June is
successfully resolved to match the commit without any conflicts (gc485f7e98):
https://lore.kernel.org/lkml/20210617101910.13228-1-song.bao.hua@hisilicon.com/T/#t
Link: https://lore.kernel.org/r/20210617101910.13228-1-song.bao.hua@hisilicon.com
attempting to guess base-commit...
Base: tags/v5.13-rc1-284-gc485f7e9863c (exact match)
(The usual caveat here is that this kind of guessing is not a guarantee that
the patch actually belongs at this commit -- merely that it applies without
conflicts there. For example, a patch may depend on newer/older code changes
in the files not touched by this particular patch/series. This is why it is
really important to provide base-commit: information in your patches, if
possible.)
Please report any bugs and regressions, as usual.
Best regards,
Konstantin
next reply other threads:[~2021-09-01 14:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-01 14:16 Konstantin Ryabitsev [this message]
2021-09-01 14:48 ` b4 v0.8.0 is available Vlastimil Babka
2021-09-01 18:02 ` Konstantin Ryabitsev
2021-09-01 19:16 ` Vlastimil Babka
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=20210901141637.fmvgs4hnk6m4ym7x@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.