From 8ebe4f059c0cc45208b1f8cc51d5236bc5b4f8fe Mon Sep 17 00:00:00 2001
From: David Caldwell <david@porkrind.org>
Date: Tue, 13 May 2008 14:15:31 -0700
Subject: [PATCH] [commit-patch] Document --message-file.

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

diff --git a/commit-patch b/commit-patch
index 2c571b6..4edfa7a 100755
--- a/commit-patch
+++ b/commit-patch
@@ -112,7 +112,7 @@ commit-patch - commit patches to I<CVS>, I<Darcs> or I<Mercurial> repositories
 
 =head1 SYNOPSIS
 
-commit-patch [B<-m> I<message>] I<patch-file>
+commit-patch [B<-m> I<message>] [B<-F> I<message-file>] I<patch-file>
 
 =head1 DESCRIPTION
 
@@ -137,6 +137,10 @@ B<commit-patch> does not interfere with the patch naming process of
 the underlying version control system; I<Darcs> will still ask you
 interactively and I<CVS> will still launch your editor.
 
+B<-F>, B<--message-file>=I<filename> - You can optionally get the
+commit message from a file. This is generally only useful for
+scripting B<commit-patch>.
+
 =head1 DIAGNOSTICS
 
 B<commit-patch> works by manipulating the working directory using
-- 
2.51.2