Re: [Ksummit-discuss] Topics for the Maintainer's Summit

Bjorn Helgaas
2019-09-19T01:48:06Z

On Fri, Sep 6, 2019 at 5:21 AM Rob Herring <robherring2@gmail.com> wrote:
> You might like my set of bailing wire using patchwork and mutt. It
> works offline if you download the patchwork state beforehand and
> queues up state changes. The basic flow is:
>
> Load the "New" list from PW (my PW instance is pre-filtered on paths,
> so I don't have to sort thru everything on the DT list)
> Check for multiple versions of patches, auto email on failure to add
> my review tag, check for already applied (to next).
> Iterate thru the patch list:
> - Run checkpatch.pl
> - open mutt for each patch. Mutt has the full DT list, so I can look
> at the rest of the series if I want.
> - After exiting mutt, prompt for PW state change
> - Possibly apply it
> - Generate replies for applied, reviewed-by or acked-by
>
> Happy to demo it at LPC if you are interested. You can find it
> here[1]. The main script is pw-review.

Thanks for the demo at LPC! I'm trying to understand how all the
pieces fit together.

How do you download the patchwork state beforehand for working
offline? For me, actually working offline is nice but rare; my
complaint is that I have to wait for every little interaction
(delegating, superseding, changing state, etc) to talk to the server.
The waits aren't long, but they make the whole process feel sluggish.

You mentioned some CI bits (to run checkpatch, change patchwork state,
etc). Is there a way to look at that? I'm guessing you also have
some mutt keybindings or macros?

Is http://patchwork.ozlabs.org/project/devicetree-bindings/list/ the
patchwork you're using? ISTR one that showed the CI results.

I guess you keep your mbox trimmed somehow? Starting mutt on my
linux-pci folder takes 5-10 seconds. But for this purpose there
wouldn't really be a need to have the *entire* history, I guess.
_______________________________________________
Ksummit-discuss mailing list
Ksummit-discuss@lists.linuxfoundation.org