discussion and development of piem
 help / color / mirror / code / Atom feed
From: Kyle Meyer <kyle@kyleam.com>
To: piem@inbox.kyleam.com
Cc: Sean Whitton <spwhitton@spwhitton.name>
Subject: [PATCH 2/2] README: Point to related projects
Date: Sun, 12 Dec 2021 17:21:19 -0500	[thread overview]
Message-ID: <20211212222119.124669-3-kyle@kyleam.com> (raw)
In-Reply-To: <20211212222119.124669-1-kyle@kyleam.com>

Documentation/piem.texi has a section that lists related projects, but
highlight a couple in the README for visibility.

Cc: Sean Whitton <spwhitton@spwhitton.name>
Link: https://inbox.kyleam.com/piem/YbZOh0yEFLBwVUMp@melete.silentflame.com/
 README | 15 +++++++++++++++
 1 file changed, 15 insertions(+)

diff --git a/README b/README
index 9c0bea47..4dd52f98 100644
--- a/README
+++ b/README
@@ -27,3 +27,18 @@ Messages that include this address are public and available as
 public-inbox archives at
+Related projects
+If you're interested in applying patches but aren't working with a
+public-inbox instance, it's still possible to use piem (see the
+documentation).  However, in this case, you may want to consider
+mailscripts (https://git.spwhitton.name/mailscripts/), a "collection
+of scripts for manipulating e-mail on Debian".  Its
+notmuch-extract-patch script (accessible via Emacs commands) provides
+an alternative to b4 for extracting a patch series from a thread.
+And if you're searching for an Emacs interface for *sending* patches,
+take a look at git-email (https://sr.ht/~yoctocell/git-email/).

      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 ` [PATCH 1/2] README: Mention b4 and lei Kyle Meyer
2021-12-12 22:21 ` Kyle Meyer [this message]

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:

  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-3-kyle@kyleam.com \
    --to=kyle@kyleam.com \
    --cc=piem@inbox.kyleam.com \
    --cc=spwhitton@spwhitton.name \


* 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


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).