path: root/maildir-import-patch.1.pod
diff options
authorSean Whitton <>2019-05-03 21:10:08 -0700
committerSean Whitton <>2019-05-03 21:51:41 -0700
commit2ccfaae0ea4ce8ab691f1b1a0e8481e9b43dbe1c (patch)
treea5caaef16a1eefef0da4db699abf524acebcfbbe /maildir-import-patch.1.pod
parentb0aa9fc4b5d6fffda94e68a8e21b337789d117fa (diff)
new scripts: maildir-import-patch(1), notmuch-import-patch(1)
Signed-off-by: Sean Whitton <>
Diffstat (limited to 'maildir-import-patch.1.pod')
1 files changed, 44 insertions, 0 deletions
diff --git a/maildir-import-patch.1.pod b/maildir-import-patch.1.pod
new file mode 100644
index 0000000..a3ef110
--- /dev/null
+++ b/maildir-import-patch.1.pod
@@ -0,0 +1,44 @@
+=head1 NAME
+maildir-import-patch - import a git patch series into a maildir
+=head1 SYNOPSIS
+B<maildir-import-patch> I<MAILDIR> [I<git-format-patch(1) args>]
+B<maildir-import-patch> generates a patch series using
+git-format-patch(1), and then imports the series into a maildir as an
+e-mail thread, one message per patch.
+This is useful for providing inline feedback on a branch by e-mail,
+when the submitter did not use git-send-email(1).
+=head1 EXAMPLE
+Suppose that Bob uses git-request-pull(1) to ask you to review and
+merge his branch 'feature'. You add Bob's repository as a remote
+called 'bob', check out the bob/feature branch locally, look at the
+commits and run some tests. Now you'd like to provide inline feedback
+on Bob's changes, indicating which parts you think are ready to merge
+and which parts need more work. So you type
+=over 4
+ % maildir-import-patch ~/Maildir/patches master..bob/feature
+Over in your MUA, you can then reply to each e-mail in the new thread
+generated by B<maildir-import-patch>, providing line-by-line feedback
+on Bob's work.
+=head1 SEE ALSO
+notmuch-import-patch(1), git-format-patch(1), git-send-email(1)
+=head1 AUTHOR
+B<notmuch-import-patch> was written by Sean Whitton