Re: New version of lore available for preview

[Lee Jones <lee.jones@linaro.org>]

On Thu, 09 Sep 2021, Steven Rostedt wrote:
> On Wed, 8 Sep 2021 14:37:46 -0400
> Konstantin Ryabitsev <konstantin@linuxfoundation.org> wrote:
> 
> > > Can we represent LKML on Patchwork as a reasonable alternative?  
> > 
> > No. That said, what I'm currently working on is a way to provide query-defined
> > public-inbox sources. If you can define what kind of patches you are
> > interested in as a lore.kernel.org query, we can save that search and feed
> > *that* into patchwork. So, instead of feeding all of LKML into patchwork just
> > for the few patches you're interested in, we can just feed the subset of
> > patches that you actually want.
> 
> This is basically what I have done locally. I set up a local instance of
> patchwork. Added a procmail filter to copy all my emails with "PATCH" in the
> subject into its own folder. Then I have a cron job that runs the following
> script to add "List-ID: <rostedt.inbox.com>" to these emails, as my local
> patchwork "listens" to the "mailing list" called "rostedt.inbox.com". And
> then send them off to my local patchwork instance.
> 
> #!/usr/bin/perl -w
> 
> my $state = "none";
> my $patch = 0;
> 
> while (<>) {
>         if (/^From /) {
>                 $state = "head";
>                 $patch = 0;
>         } elsif ($state eq "head") {
>                 if (/^\s*$/) {
>                         print "List-ID: <rostedt.inbox.com>\n" if ($patch);
>                         $state = "body";
>                 } else {
>                         if (/list-id/i) {
>                                 next;
>                         } elsif (/^Subject.*patch/i) {
>                                 $patch = 1;
>                         }
>                 }
>         }
>         print;
> }
> 
> 
> This works great for me, but I can imagine if people have their own public
> inboxes, where we can just create a patchwork instance that feeds off of
> these inboxes, I believe you will get the same functionality that I have.
> 
> Note, I also have filters to read patches that have "[for-next]" and
> "[for-linus]" which converts the patches in patchwork from "New" to "Under
> Review". Then I have a subscription to all commits that go into Linus's
> tree, and I process all of them to go through and "Approve" any patch that
> it finds.
> 
> I still would love a way to download patchwork offline, where it loads
> locally all pending patches, and lets you review / apply them locally
> without needing to be connected online, as this would be useful during
> flights. Then when you land, you can upload your changes.

Well, as beautifully inefficient as that all sounds, it might be
slightly less time consuming if I just succumb to peer pressure and
switch pwclient out for b4.

Thankfully, my use-case is much simpler than Steven's.

In my current implementation, I have pwclient pull down the patch,
apply my SoB and apply the it, all in one foul swoop:

  pwclient git-am -p ${project} -3 -s ${pwid}

Does b4 provide this functionality too, or do I have to script around
it?  How have other's chosen to automatically apply the downloaded
mboxes?

-- 
Lee Jones [李琼斯]
Senior Technical Lead - Developer Services
Linaro.org │ Open source software for Arm SoCs
Follow Linaro: Facebook | Twitter | Blog