From fa7c534f31f73ad2222186521ad274f976ed0f0c Mon Sep 17 00:00:00 2001
From: David Caldwell <david@porkrind.org>
Date: Mon, 22 Dec 2008 16:59:23 -0800
Subject: [PATCH] Document commit-partial.

---
 commit-patch | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/commit-patch b/commit-patch
index 9f3fa9d..13dd5a7 100755
--- a/commit-patch
+++ b/commit-patch
@@ -189,6 +189,8 @@ commit-patch - commit patches to I<Darcs>, I<Git>, I<CVS>, or I<Mercurial> repos
 
 commit-patch [B<-m> I<message>] [B<-F> I<message-file>] [B<-v>] [B<-n>] [I<patch-file>]
 
+commit-partial [B<-v>] [B<-n>] [I<file> ...]
+
 =head1 DESCRIPTION
 
 Normally version control systems don't allow fine grained
@@ -197,6 +199,14 @@ gets committed (or "recorded", in I<Darcs> parlance) by letting the user
 supply a patch to be committed rather than using the files in the
 current working directory.
 
+B<commit-partial> is like commit-patch except that it will create a
+patch from the current changes in the current working directory and
+launch your editor so that you can edit the patch and the commit
+message (using the B<VISUAL> environment variable, or if that isn't
+set the B<EDITOR> environment variable, or, if I<that> isn't set,
+B<vi>. Any files you specify will be passed to your version control's
+diff command.
+
 B<commit-patch> currently supports the following version control systems:
 B<I<Darcs>>, B<I<Git>>, B<I<CVS>>, and B<I<Mercurial>>.
 
-- 
2.51.2