From: Kyle Meyer <kyle@kyleam.com>
To: piem@inbox.kyleam.com
Subject: [PATCH 1/2] README: Mention b4 and lei
Date: Sun, 12 Dec 2021 17:21:18 -0500 [thread overview]
Message-ID: <20211212222119.124669-2-kyle@kyleam.com> (raw)
In-Reply-To: <20211212222119.124669-1-kyle@kyleam.com>
piem leans on b4 heavily, so it deserves a pointer in the README.
Plus, the next patch will mention b4 when it describes mailscripts,
and it seems a bit odd for that to be the only mention.
And lei wasn't a thing when this README was written, but it's
certainly worth highlighting now.
---
README | 12 +++++++++---
1 file changed, 9 insertions(+), 3 deletions(-)
diff --git a/README b/README
index a79f8eda..9c0bea47 100644
--- a/README
+++ b/README
@@ -5,9 +5,15 @@ piem --- Emacs tools and glue for working with public-inbox archives
This project is currently in the early stages of development. In
general, anything that relates to interacting with public-inbox
(https://public-inbox.org/README) archives from Emacs is worth
-considering, at least at this point. Much of the current
-functionality focuses on mapping public-inbox endpoints (email, nntp,
-http, rss) to associated code repositories in order to apply patches.
+considering, at least at this point.
+
+Much of the current functionality focuses on mapping public-inbox
+endpoints (email, nntp, http, rss) to associated code repositories in
+order to apply patches, including integration with b4-am to extract
+and process patches (https://git.kernel.org/pub/scm/utils/b4/b4.git).
+Upcoming development will largely focus on extending the very basic
+support public-inbox's local email interface (lei).
+
Documentation is available online at
https://docs.kyleam.com/piem/
--
2.34.0
next prev parent reply other threads:[~2021-12-12 22:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-12 22:21 [PATCH 0/2] README updates Kyle Meyer
2021-12-12 22:21 ` Kyle Meyer [this message]
2021-12-12 22:21 ` [PATCH 2/2] README: Point to related projects Kyle Meyer
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
List information: https://git.kyleam.com/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20211212222119.124669-2-kyle@kyleam.com \
--to=kyle@kyleam.com \
--cc=piem@inbox.kyleam.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.kyleam.com/piem/
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 read-only IMAP folder(s) and NNTP newsgroup(s).