Skip to content

Commit

Permalink
Fix git-format-patch usage string wrt output modes.
Browse files Browse the repository at this point in the history
--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>
  • Loading branch information
Yann Dirson authored and Junio C Hamano committed Jan 8, 2006
1 parent 36071af commit 5f815e5
Showing 1 changed file with 4 additions and 2 deletions.
6 changes: 4 additions & 2 deletions git-format-patch.sh
Original file line number Diff line number Diff line change
Expand Up @@ -9,8 +9,10 @@ one file per patch, for e-mail submission. Each output file is
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.
Expand Down

0 comments on commit 5f815e5

Please sign in to comment.