Fix git-format-patch usage string wrt output modes.
--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> Signed-off-by: Junio C Hamano <junkio@cox.net>
Yann Dirson committed
Jan 8, 2006 at 01:39 UTC
5f815e5922eb31c5826e5f5f21e83d1f6f338ed1
1 file changed
+4
-2
git-format-patch.sh
+4
-2
@@ -9,8 +9,10 @@ one file per patch, for e-mail submission. Each output file is
9
numbered sequentially from 1, and uses the first line of the commit
10
message (massaged for pathname safety) as the filename.
11
12
-When -o is specified, output files are created in that directory; otherwise in
13
-the current working directory.
12
+There are three output modes. By default, output files are created in
13
+the current working directory; when -o is specified, they are created
14
+in that directory instead; when --stdout is specified, they are spit
15
+on standard output, and can be piped to git-am.
16
17
When -n is specified, instead of "[PATCH] Subject", the first line is formatted
18
as "[PATCH N/M] Subject", unless you have only one patch.