Re: [kernel.org users] Gmail message ID finder Chrome extension

[Linus Walleij <linus.walleij@linaro.org>]

On Sun, Mar 29, 2020 at 7:13 PM Konstantin Ryabitsev
<konstantin@linuxfoundation.org> wrote:

> The way I envision this could work is if we define workflows based on
> labels. E.g.:
>
> 1. You label a message with "Accepted"
> 2. You run "b4 gmail apply Accepted" (or an agent process runs that)
> 3. We then try to:
>    - retrieve patch series using lore and your inbox as sources
>    - make an am-ready mbox
>    - apply to a branch provided in a mapping config
>      "e.g. Accepted->refs/heads/pending"
> 4. If "git am" fails on a series, we label the thread as
>    "Review-Required" and move to the next one
> 5. If it succeeds, we add the label "Applied"

That works for me. I have noticed that some people have this
two-step workflow of first tagging stuff (or moving it to some
folder I guess if they use e.g. mutt) and then as second step
do the application and tag stuff as applied and send out mails.

I usually prefer the more
direct "this one patch, apply it, resolved conflicts done" on a
one-by-one basis that's why I wanted it right in the UI.

But I suppose I can just tag one message at the time if I
insist :D

If there is a series I guess you just tag the 00/nn patch and
it picks the whole series?

Being able to just use gmail is really low threshold and can bring
new maintainers in and up to speed I think.

Yours,
Linus Walleij