discussion and development of piem
 help / color / mirror / code / Atom feed
From: Kyle Meyer <kyle@kyleam.com>
To: piem@inbox.kyleam.com
Subject: [PATCH] manual: Add section on applying patches without public-inbox
Date: Mon, 21 Sep 2020 00:58:01 -0400	[thread overview]
Message-ID: <20200921045801.24501-1-kyle@kyleam.com> (raw)

 piem.texi | 24 +++++++++++++++++++++++-
 1 file changed, 23 insertions(+), 1 deletion(-)

diff --git a/piem.texi b/piem.texi
index 1595b39..131ab44 100644
--- a/piem.texi
+++ b/piem.texi
@@ -1,6 +1,6 @@
 \input texinfo @c -*-texinfo-*-
-@set VERSION 0.1.0
+@set VERSION 0.2.0 (unreleased)
 @setfilename piem.info
 @documentencoding UTF-8
@@ -336,6 +336,28 @@ than identifying the thread based on the specified message ID.
 @end table
+@node Applying patches without a public-inbox archive
+@section Applying patches without a public-inbox archive
+Much of the functionality described in the previous sections can work
+even if messages aren't available in a public-inbox archive.
+@code{piem-am} and @code{piem-b4-am-from-mid} try to generate the
+am-ready mbox from a local source (e.g., via Notmuch or Gnus) before
+falling back to downloading the thread from a public-inbox archive.
+Note, however, that the @code{piem-notmuch} integration library is
+currently the only library that can generate an entire @emph{thread}
+from a given message ID.  As a result, if you're not a Notmuch user and
+are working with a project that doesn't have a public-inbox archive,
+you're unlikely to find the @code{piem-b4-am-from-mid} command useful.
+@cindex mailscripts
+Also, for those not working with public-inbox archives, it's worth
+checking out @url{https://git.spwhitton.name/mailscripts/,mailscripts},
+a nice set of Debian-focused tools by Sean Whitton that provides, among
+other things, functionality for applying patch series, including
+b4-inspired patch extraction.
 @node Injecting messages into a Maildir directory
 @chapter Injecting messages into a Maildir directory

base-commit: 7a98f40e99a1c06ef76e6c92694023c1d8309103

                 reply	other threads:[~2020-09-21  4:58 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:

  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=20200921045801.24501-1-kyle@kyleam.com \
    --to=kyle@kyleam.com \
    --cc=piem@inbox.kyleam.com \


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