new scripts: maildir-import-patch(1), notmuch-import-patch(1)

Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>

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>]
+
+=head1 DESCRIPTION
+
+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
+
+=back
+
+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
+<spwhitton@spwhitton.name>.