summaryrefslogtreecommitdiff
path: root/notmuch-extract-patch.1.pod
diff options
context:
space:
mode:
authorSean Whitton <spwhitton@spwhitton.name>2018-07-26 16:27:01 +0800
committerSean Whitton <spwhitton@spwhitton.name>2018-07-26 16:32:58 +0800
commitdce35bdf1fc374b652f8fae98e59a9d26e88ab61 (patch)
treeac17ca3a8e3dce2d717af2286e1137b08117d462 /notmuch-extract-patch.1.pod
parentd7c56828c7e3890cd343435daa9bdef30184d4eb (diff)
downloadmailscripts-dce35bdf1fc374b652f8fae98e59a9d26e88ab61.tar.gz
notmuch-extract-patch: note assumption that there is only one series
Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
Diffstat (limited to 'notmuch-extract-patch.1.pod')
-rw-r--r--notmuch-extract-patch.1.pod13
1 files changed, 13 insertions, 0 deletions
diff --git a/notmuch-extract-patch.1.pod b/notmuch-extract-patch.1.pod
index ee0c6f6..21095bc 100644
--- a/notmuch-extract-patch.1.pod
+++ b/notmuch-extract-patch.1.pod
@@ -26,6 +26,19 @@ None.
=back
+=head1 LIMITATIONS
+
+B<notmuch-extract-patch> assumes one patch series per query. So if
+there is more than one patch series in a thread, you will need to
+construct a notmuch query that includes only the patches you want to
+extract, which somewhat defeats the purpose of this script.
+
+This should not happen often because best practices when sharing
+patches with git-send-email(1) include starting a new thread when
+posting a revised series. The I<--in-reply-to> option to
+B<notmuch-extract-patch> is used mainly for posting a patch series in
+reply to a bug report.
+
=head1 SEE ALSO
notmuch(1), git-send-email(1)