From 519cf0fa2348e5022fc5e383e323364241d7b42f Mon Sep 17 00:00:00 2001 From: Sean Whitton Date: Sat, 9 Nov 2019 11:05:45 -0700 Subject: notmuch-extract-patch: add -v/--reroll-count option Signed-off-by: Sean Whitton --- notmuch-extract-patch.1.pod | 31 +++++++++++++++++++++---------- 1 file changed, 21 insertions(+), 10 deletions(-) (limited to 'notmuch-extract-patch.1.pod') diff --git a/notmuch-extract-patch.1.pod b/notmuch-extract-patch.1.pod index 21095bc..a18cc22 100644 --- a/notmuch-extract-patch.1.pod +++ b/notmuch-extract-patch.1.pod @@ -4,7 +4,7 @@ notmuch-extract-patch - extract a git patch series from notmuch =head1 SYNOPSIS -B I +B [B<-v>|B<--reroll-count=>I] I =head1 DESCRIPTION @@ -15,7 +15,23 @@ replies/reviews. =head1 OPTIONS -None. +=over 4 + +=item B<-v>|B<--reroll-count=>I + +Try to extract the Ith version of a patch series, where these +patches are identified by subject prefixes like "[PATCH vI 1/3]". + +If this option is not specified, default to extracting the first +version of the patch series. + +Note that this option should not usually be needed, 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 git-format-patch(1) is used mainly for posting a patch +series in reply to a bug report. + +=back =head1 EXAMPLE @@ -28,17 +44,12 @@ None. =head1 LIMITATIONS -B assumes one patch series per query. So if -there is more than one patch series in a thread, you will need to +B can select patches to extract based on the +reroll count, but otherwise assumes that there is only one patch +series in a thread. If this assumption is violated, you would 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 is used mainly for posting a patch series in -reply to a bug report. - =head1 SEE ALSO notmuch(1), git-send-email(1) -- cgit v1.2.3