From: Matthieu Baerts <matttbe@kernel.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: "Kernel.org Tools" <tools@kernel.org>
Subject: Re: b4 review: please update the requirements files
Date: Wed, 1 Jul 2026 12:55:49 +0200 [thread overview]
Message-ID: <7776be8f-89d2-443e-bbe5-844dee25054d@kernel.org> (raw)
In-Reply-To: <db20312a-5846-4d32-8913-f3265bfe5f93@kernel.org>
On 30/06/2026 11:28, Matthieu Baerts wrote:
(...)
> I initially thought that it was because my tracked list contains patches
> from the end of April, and that's why I first tried to "clean" my
> environment by renaming ~/.cache/b4, ~/.local/share/b4 and ~/.local/
> hare/b4-archived directory. But I still had patches in the list. I
> finally fixed the issue by updating the requirements files, but first:
> how do I reset b4 review?
I think I found out why I still had items in the list: I guess I also
need to remove all the "b4/review/*" branches to fully reset b4 review.
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
prev parent reply other threads:[~2026-07-01 10:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-30 9:28 b4 review: please update the requirements files Matthieu Baerts
2026-07-01 10:55 ` Matthieu Baerts [this message]
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=7776be8f-89d2-443e-bbe5-844dee25054d@kernel.org \
--to=matttbe@kernel.org \
--cc=konstantin@linuxfoundation.org \
--cc=tools@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