Re: b4 review: reply to a patch note + misc.

Konstantin Ryabitsev <[email protected]> Mon, 3 Aug 2026 11:43:02 -0400
Newsgroups org.kernel.linux.tools
Message-ID <20260803-agile-bonobo-of-superiority-6791e9@meerkat>
On Tue, Jun 30, 2026 at 12:17:43PM +0200, Matthieu Baerts wrote:

Hi Matt,

Quick status update on your list -- good news on most of it:

> When a patch has a note under 3 dashes, the note is dropped when the
> patch is applied during a review, as expected. Except that it also means
> the note is no longer there when replying to a patch from b4 review tui.
>
> Do you think the "Reply" view could use the email from lore instead?

This one is confirmed and tracked, but not fixed yet -- I want to wrap up the
feature set for 0.16. Building the reply from the original message rather than
the applied commit is the right approach, so the notes should survive once
that lands.

> - I find it "too easy" to quit the "Review" view: I'm on a patch,
>   checking follow-up comments, etc. then if I hit an extra 'q', I'm
>   back on the "Tracked" list, switching back to another commit in git,
>   etc. Maybe a "confirmation" question could help? Or a different short
>   key?

Yes, I hit the same annoyance, so this is now fixed in master: bare 'q' now
just warns, and quitting takes a capital 'Q'. This is consistent across all
the b4 TUIs now.

> - When I press the 'review' button, I need to specify the commit/branch
>   for the new base. I usually prefer to apply it on top of the current
>   HEAD, but I'm not sure how to force b4 to suggest that by default. I
>   tried using "git config b4.review-target-branch", but it still guesses
>   something else.

Also in master: there is a new b4.review-apply-base config option. Set
it to HEAD (or any ref) and the base dialog will pre-fill with that
instead of the series base-commit or the automatic guess. The
auto-detected base still shows up in the dialog hint, so you don't lose
that information.

> - Could we eventually have a template for the replies? It would be good
>   to automatically add a header (Hi <first name>,) and a trailer (like
>   here at the bottom).

Done as well: b4.review-reply-template can point at a template file,
same mechanism as b4 ty's thanks templates, with ${firstname} and
friends available for substitution.

So: three out of four are in master -- only the ---notes one is still
pending. Thanks a lot for the continued feedback!

Best regards,
-K