From 4dcae7e33a0cb601184646eaa9c472400a9eb143 Mon Sep 17 00:00:00 2001
From: David Caldwell <david@porkrind.org>
Date: Sun, 24 Oct 2010 15:32:46 -0700
Subject: [PATCH] [commit-patch] Document --retry.

---
 commit-patch | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/commit-patch b/commit-patch
index 9900a3c..36a6568 100755
--- a/commit-patch
+++ b/commit-patch
@@ -249,7 +249,7 @@ commit-patch - commit patches to I<Darcs>, I<Git>, I<Mercurial>, I<Bazaar>, I<Su
 
 commit-patch [B<--amend>] [B<-m> I<message>] [B<-F> I<message-file>] [B<-v>] [B<--dry-run>] [I<patch-file>]
 
-commit-partial [B<--amend>] [B<-v>] [B<--dry-run>] [I<file> ...]
+commit-partial [B<--amend>] [B<-v>] [B<--dry-run>] [B<--retry>] [I<file> ...]
 
 =head1 DESCRIPTION
 
@@ -299,6 +299,11 @@ B<-n>, B<--dry-run> - Turn on more paranoid debugging. This will print
 the commands that B<commit-patch> will run to get the patch committed
 but it won't actually run those commands.
 
+B<-r>, B<--retry> - Only available in I<commit-partial>. This will reload the
+last patch that was attempted to be committed into your editor instead of the
+current changes in the directory. This is for cases where the patch fails to
+commit for some reason and you want to try to fix it instead of starting over.
+
 =head1 DIAGNOSTICS
 
 B<commit-patch> works by manipulating the working directory using
-- 
2.51.2