Linux maintainer tooling and workflows
 help / color / mirror / Atom feed
From: Matthieu Baerts <matttbe@kernel.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: "Kernel.org Tools" <tools@kernel.org>
Subject: Re: b4 review tui: too smart reply features?
Date: Tue, 30 Jun 2026 12:55:25 +0200	[thread overview]
Message-ID: <b2c44799-85a9-4576-9aae-b43eb1092315@kernel.org> (raw)
In-Reply-To: <20260610-psychedelic-encouraging-quoll-c7b949@lemur>

Hi Konstantin,

On 11/06/2026 03:56, Konstantin Ryabitsev wrote:
> On Tue, Apr 28, 2026 at 12:52:01PM +0200, Matthieu Baerts wrote:
>> Hi Konstantin,
>>
>> I'm still trying 'b4 review tui', and something that bothers me is when
>> my replies are mangled. I have three examples.
> 
> Okay, the latest master has revamped that quite a bit. I was also not really
> happy with the way I kept fighting with the tooling, which is the opposite of
> where I want to go. I had the bright idea to move some of the functionality
> into a vim plugin instead of doing it in b4 directly -- this way you still get
> most of the neat features but without the inability to undo or forced/awkward
> quote trimming.
> 
> Can you try it out and see if you're fighting with the current master less?

Thank you for the update, and sorry for the delay!

I just retried, and it is indeed much better now! Yet, I still have an
issue with trailers, e.g.

  Please add a Fixes tag. Here I guess it should be:

  Fixes: (...)

The Review view then correctly showed my comment with the Fixes tag, but
*I think* the Fixes tag was not visible in green at the bottom left (not
sure, because I also added a Reviewed-by tag after the reply). When
looking at the 'email mode' view, the Fixes tag got dropped, leaving 2
empty lines around.

Back to the 'reply' view, vim showed all lines ending with ^M, and the
line starting with 'Fixes:' was no longer there. Adding it back re-added
it to the other views, and the Fixes tag was also listed at the bottom
left in the 'review' view, but I could see extra new lines due to all
these \r. Stripping them from the 'reply' view fixes all the issues, and
I was able to send the reply with both my Fixes and Reviewed-by tags.

Any idea was caused that? :)

BTW, after having sent a reply, it appears a few seconds later as unread
in my inbox. I guess only a filter on the inbox side can help to mark
them as read, right?

Cheers,
Matt
-- 
Sponsored by the NGI0 Core fund.


      reply	other threads:[~2026-06-30 10:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-28 10:52 b4 review tui: too smart reply features? Matthieu Baerts
2026-06-11  1:56 ` Konstantin Ryabitsev
2026-06-30 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=b2c44799-85a9-4576-9aae-b43eb1092315@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