From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: ksummit@lists.linux.dev
Subject: [TECH TOPIC] Doing more with lore and b4
Date: Mon, 19 Apr 2021 12:18:15 -0400 [thread overview]
Message-ID: <20210419161815.ng5hp364x6mzucpv@nitro.local> (raw)
While lore.kernel.org is a fairly new service, it has quickly become an
indispensable workflow part for many maintainers. Tools like b4 allow to
automate many aspects of maintainer duties:
- retrieving entire patch series
- tallying up and applying review trailers from thread follow-ups
- diffing re-rolled series against previous versions
- sending templated thank-you notes for applied series and merged pull
requests
- cryptographically verifying patches for attestation purposes (using DKIM,
PGP, and more)
This talk will review some of the above functionality that may be already
familiar to maintainers, but will also go through other features of
public-inbox, and peek into what is coming in newer releases, such as:
- how to mirror lore.kernel.org locally (in part or in full)
- how to integrate public-inbox sources into your automated tools
- how to use anonymous imap service for reading mail without subscribing
- how to use local-email-interface (lei) command to create saved searches and
get pre-filtered threads from multiple local and remote sources into your
inbox
Working with patches sent via email does not need to be frustrating or
insecure. We are aiming to provide a set of tools to further streamline this
process -- your feedback and suggestions are extremely useful and help
prioritize our efforts.
-K
reply other threads:[~2021-04-19 16:18 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=20210419161815.ng5hp364x6mzucpv@nitro.local \
--to=konstantin@linuxfoundation.org \
--cc=ksummit@lists.linux.dev \
/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).