Re: b4 review tui + lore/lei/korgalore

On Tue, Jun 30, 2026 at 11:19:53AM -0400, Konstantin Ryabitsev wrote:
> On Tue, Jun 30, 2026 at 04:12:47PM +0200, Christian Brauner wrote:
> > Hey Konstantin,
> > 
> > So I've now been working with b4 review tui exclusively for a while and
> > have added a bunch of extensions that put it on steroids for me. In
> > place merge conflict resolution when applying individual patches or
> > series is just "chef's kiss".
> 
> Great to hear. Please feel free to share all your "on steroids" changes -- if
> it's useful to you, then it should be useful to others as well.

Thanks, will do!

> Are you using editor integrations (vim/emacs) at all?

So for b4 review tui it falls back to my git neovim default editor and
it just works very well. From your message I gather that I missed other
integration so now I'm busy finding them... Oh wow, no. I didn't know
that. Let me try them immediately.

> > I also do like the patchwork integration which is very nice and allows
> > me to pick series from patchwork into b4 review tui without much effort.
> > 
> > One thing that I'm missing is a companion to the patchwork app
> > integration for mailing lists. Here's what I mean. I want to be able to
> > browse a mailing list the same way I'm browsing the patchwork app ('p')
> > in b4 review tui, then mark them as "tracked" etc (ideally it would
> > de-duplicate by message-id or something between the patchwork app and
> > the mailing list.
> 
> Yes, we're thinking along the same lines -- check plan.otl. You will find a
> "consume a public-inbox archive" section under 0.17 that is admittedly just a
> stream of consciousness right now.

Lovely! I cannot wait for this!

> 
> > I'm not well-versed enough in lore/lei/korgalore to find the correct
> > integration point for this so this makes sense.
> 
> It doesn't exist yet, but the idea will be to set up korgalore to get the
> stuff from the list you want, and then just throw it at a "b4 review consume"
> pipe, and let b4 figure out the rest. The end-result should be a sort of
> "maintainer's dashboard":
> 
> - bug reports
> - outstanding series

Perfect!

> - general correspondence

I have dreamed about this specific feature. Just two days ago I started
tracking a thread outside of b4 review and was wondering how I could
make the case for having this inside of b4 review tui natively. Love it!

> This effectively reverses the current b4 flow: instead of going from a mail
> client to b4, everything goes to b4 first, and then you can yank things into
> your mail client that you actually want to view there. The mailing lists and
> lore in general become mostly a sort of a distributed messaging bus.

Love it.

> > Here's some proposals that I came up with talking to an LLM:
> 
> Thanks for sharing! I'm away for 2 weeks, so I deliberately skipped reading

Enjoy the vacation!

> the rest, because it requires a fresher brain. :) I'll take a look and
> cross-reference with where I want things to go once I'm back.

Absolutely. :)

Thanks!
Christian