From: Steven Rostedt <rostedt@goodmis.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: Lee Jones <lee.jones@linaro.org>,
Masahiro Yamada <masahiroy@kernel.org>,
Jason Gunthorpe <jgg@nvidia.com>,
users@linux.kernel.org, tools@linux.kernel.org
Subject: Re: New version of lore available for preview
Date: Thu, 9 Sep 2021 08:49:07 -0400 [thread overview]
Message-ID: <20210909084907.271b6df5@gandalf.local.home> (raw)
In-Reply-To: <20210908183746.iancht34j3drun77@meerkat.local>
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.
-- Steve
next prev parent reply other threads:[~2021-09-09 12:49 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-18 19:07 New version of lore available for preview Konstantin Ryabitsev
2021-08-18 19:09 ` Jason A. Donenfeld
2021-08-18 19:48 ` Konstantin Ryabitsev
2021-08-18 19:50 ` Junio C Hamano
2021-08-25 16:30 ` Rob Herring
2021-08-25 16:44 ` Konstantin Ryabitsev
2021-08-25 21:39 ` Josh Triplett
2021-08-26 14:04 ` Konstantin Ryabitsev
2021-08-26 23:04 ` Josh Triplett
2021-09-02 19:53 ` Jason Gunthorpe
2021-09-02 20:14 ` Konstantin Ryabitsev
2021-09-02 22:44 ` Masahiro Yamada
2021-09-03 10:30 ` Mark Brown
2021-09-03 15:21 ` Konstantin Ryabitsev
2021-09-06 9:59 ` Lee Jones
2021-09-08 18:37 ` Konstantin Ryabitsev
2021-09-09 12:49 ` Steven Rostedt [this message]
2021-09-09 13:32 ` Lee Jones
2021-09-09 13:38 ` Konstantin Ryabitsev
2021-09-09 13:45 ` Lee Jones
2021-09-09 14:39 ` Konstantin Ryabitsev
2021-09-09 15:24 ` James Bottomley
2021-09-09 16:17 ` Konstantin Ryabitsev
2021-09-09 14:51 ` Alexandre Belloni
2021-09-09 15:00 ` Konstantin Ryabitsev
2021-09-09 13:43 ` Greg KH
2021-09-09 13:54 ` Lee Jones
2021-09-09 13:56 ` Mark Brown
2021-09-09 14:05 ` Lee Jones
2021-09-10 16:07 ` Bjorn Andersson
2021-09-10 16:12 ` Mark Brown
2021-09-10 17:21 ` Peter Zijlstra
2021-09-09 13:55 ` Steven Rostedt
2021-09-09 14:04 ` Lee Jones
2021-09-09 14:51 ` Peter Zijlstra
2021-09-10 6:10 ` Lee Jones
2021-09-02 23:38 ` Jason Gunthorpe
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=20210909084907.271b6df5@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=jgg@nvidia.com \
--cc=konstantin@linuxfoundation.org \
--cc=lee.jones@linaro.org \
--cc=masahiroy@kernel.org \
--cc=tools@linux.kernel.org \
--cc=users@linux.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;
as well as URLs for NNTP newsgroup(s).