From 2f6a3823700cbfda236c2c1f023c43601adae9af Mon Sep 17 00:00:00 2001 From: Junio C Hamano Date: Tue, 28 Aug 2007 21:58:53 -0700 Subject: format-patch documentation: reword to hint "--root " more clearly Signed-off-by: Junio C Hamano --- Documentation/git-format-patch.txt | 17 ++++++++++------- 1 file changed, 10 insertions(+), 7 deletions(-) (limited to 'Documentation') diff --git a/Documentation/git-format-patch.txt b/Documentation/git-format-patch.txt index 5e6d5373ad..c9857a2d62 100644 --- a/Documentation/git-format-patch.txt +++ b/Documentation/git-format-patch.txt @@ -34,13 +34,16 @@ There are two ways to specify which commits to operate on. 2. Generic expression (see "SPECIFYING REVISIONS" section in gitlink:git-rev-parse[1]) means the - commits in the specified range. A single commit, when - interpreted as a expression, means - "everything that leads to that commit", but that is taken as - the special case above. If you want to format everything - since project inception to one commit, say "git format-patch - \--root ", as showing the root commit as patch - requires \--root option anyway. + commits in the specified range. + +A single commit, when interpreted as a +expression, means "everything that leads to that commit", but +if you write 'git format-patch ', the previous rule +applies to that command line and you do not get "everything +since the beginning of the time". If you want to format +everything since project inception to one commit, say "git +format-patch \--root " to make it clear that it is the +latter case. By default, each output file is numbered sequentially from 1, and uses the first line of the commit message (massaged for pathname safety) as -- cgit v1.2.3