From: Paolo Bonzini <pbonzini@redhat.com>
To: workflows@vger.kernel.org, Fam Zheng <fam@euphon.net>
Subject: Patchew is now indexing LKML
Date: Fri, 18 Feb 2022 19:09:10 +0100 [thread overview]
Message-ID: <9a4360d9-2420-59fd-2490-3b657710db13@redhat.com> (raw)
Hi all,
just a small announcement that the patchew.org service is now archiving
and indexing all patch series coming through LKML. The main page is at
https://patchew.org/linux/.
Patchew is not unlike patchwork, in that it will collect and index patch
series as they appear on a mailing list. Its functionality also
overlaps a bit with b4 in that it recognizes and stores various tags
sent in reply to the patch series, and also links together different
submissions of the same series. It has been in use for a few years with
various virtualization projects (it was created during the patchword 2.x
stasis), and recently MPTCP has also based its CI on Patchew plus GitHub
Actions.
The LKML integration is still a bit new and experimental, so it is not
yet applying the patches to a git tree like it does for other projects
such as QEMU; this also means that for example it is not yet possible to
"search by maintainer". However, the patches are already searchable by
to/cc, and also available via REST API at
https://patchew.org/api/v1/projects/12/.
Our hope is to further integrate Patchew with the various mailing list
workflow tools in the coming months, for example using b4's three-way merge.
The website has some small server-side functionality for users to mark
series as accepted/rejected, though it lacks something like the
delegation feature of patchwork. To use this functionality you'll need
an account, which right now must be created by myself. Please contact
me offlist if you're interested (though by all means reply on the
mailing list if you want further information on the tool).
Paolo
reply other threads:[~2022-02-18 18:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=9a4360d9-2420-59fd-2490-3b657710db13@redhat.com \
--to=pbonzini@redhat.com \
--cc=fam@euphon.net \
--cc=workflows@vger.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).