development/git
development/git
1
0
Fork 0
mirror of https://github.com/git/git synced 2024-08-24 18:26:02 +00:00
Code Issues Packages Projects Releases Wiki Activity

format-patch documentation: reword to hint "--root <one-commit>" more clearly

Browse source 
Signed-off-by: Junio C Hamano <gitster@pobox.com>
This commit is contained in:
Junio C Hamano 2007-08-28 21:58:53 -07:00
parent 04b508f22b
commit 2f6a382370
1 changed files with 10 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

17
Documentation/git-format-patch.txt
View file

@ -34,13 +34,16 @@ There are two ways to specify which commits to operate on.
2. Generic <revision range> expression (see "SPECIFYING 2. Generic <revision range> expression (see "SPECIFYING
REVISIONS" section in gitlink:git-rev-parse[1]) means the REVISIONS" section in gitlink:git-rev-parse[1]) means the
commits in the specified range. A single commit, when commits in the specified range.
interpreted as a <revision range> expression, means
"everything that leads to that commit", but that is taken as A single commit, when interpreted as a <revision range>
the special case above. If you want to format everything expression, means "everything that leads to that commit", but
since project inception to one commit, say "git format-patch if you write 'git format-patch <commit>', the previous rule
\--root <that-commit>", as showing the root commit as patch applies to that command line and you do not get "everything
requires \--root option anyway. since the beginning of the time". If you want to format
everything since project inception to one commit, say "git
format-patch \--root <commit>" to make it clear that it is the
latter case.
By default, each output file is numbered sequentially from 1, and uses the By default, each output file is numbered sequentially from 1, and uses the
first line of the commit message (massaged for pathname safety) as first line of the commit message (massaged for pathname safety) as