[PATCH 3/7] Fix git-formatpatch usage string wrt output modes

From: Yann Dirson <ydirson@altern.org>
Date: Jan 8, 2006, 00:39 UTC
Message-ID: <20060108003916.GK1113@nowhere.earth>

--stdout was not mentionned, and the description for the case where -o was not given was thus incomplete.

Signed-off-by: Yann Dirson <ydirson@altern.org>

---

 git-format-patch.sh |    6 ++++--
 1 files changed, 4 insertions(+), 2 deletions(-)

8a6d4a039ff4ffd75d5eeddbd6801787a8479b05

diff --git a/git-format-patch.sh b/git-format-patch.sh
index daa3cae..0948f1f 100755
--- a/git-format-patch.sh
+++ b/git-format-patch.sh
@@ -9,8 +9,10 @@ one file per patch, for e-mail submissio
 numbered sequentially from 1, and uses the first line of the commit
 message (massaged for pathname safety) as the filename.
 
-When -o is specified, output files are created in that directory; otherwise in
-the current working directory.
+There are three output modes.  By default, output files are created in
+the current working directory; when -o is specified, they are created
+in that directory instead; when --stdout is specified, they are spit
+on standard output, and can be piped to git-am.
 
 When -n is specified, instead of "[PATCH] Subject", the first line is formatted
 as "[PATCH N/M] Subject", unless you have only one patch.

-- 
1.0.6-g8ecb

-- 
Yann Dirson    <ydirson@altern.org> |
Debian-related: <dirson@debian.org> |   Support Debian GNU/Linux:
                                    |  Freedom, Power, Stability, Gratis
     http://ydirson.free.fr/        | Check <http://www.debian.org/>