path: root/Documentation/git-format-patch.txt
diff options
authorJunio C Hamano <>2009-04-02 05:49:03 (GMT)
committerJunio C Hamano <>2009-04-02 05:49:03 (GMT)
commit85b7bd50c47e0f5236cdb93d1be3163a8a1a3be6 (patch)
tree7b565c28cc3d8d1137e9dd297f638e6fffdc7625 /Documentation/git-format-patch.txt
parent02c62b10de16515497f1b6fde6278ac531b90f1c (diff)
parent2d266f9d623625e0a28fbe3c3615707500e9448f (diff)
Merge branch 'tr/maint-1.6.1-doc-format-patch--root'
* tr/maint-1.6.1-doc-format-patch--root: Documentation: format-patch --root clarifications
Diffstat (limited to 'Documentation/git-format-patch.txt')
1 files changed, 12 insertions, 9 deletions
diff --git a/Documentation/git-format-patch.txt b/Documentation/git-format-patch.txt
index c2eb5fa..c105925 100644
--- a/Documentation/git-format-patch.txt
+++ b/Documentation/git-format-patch.txt
@@ -40,15 +40,11 @@ There are two ways to specify which commits to operate on.
REVISIONS" section in linkgit:git-rev-parse[1]) means the
commits in the specified range.
-A single commit, when interpreted as a <revision range>
-expression, means "everything that leads to that commit", but
-if you write 'git format-patch <commit>', 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 <commit>" to make it clear that it is the
-latter case. If you want to format a single commit, you can do
-this with "git format-patch -1 <commit>".
+The first rule takes precedence in the case of a single <commit>. To
+apply the second rule, i.e., format everything since the beginning of
+history up until <commit>, use the '\--root' option: "git format-patch
+\--root <commit>". If you want to format only <commit> itself, you
+can do this with "git format-patch -1 <commit>".
By default, each output file is numbered sequentially from 1, and uses the
first line of the commit message (massaged for pathname safety) as
@@ -182,6 +178,13 @@ not add any suffix.
applied. By default the contents of changes in those files are
encoded in the patch.
+ Treat the revision argument as a <revision range>, even if it
+ is just a single commit (that would normally be treated as a
+ <since>). Note that root commits included in the specified
+ range are always formatted as creation patches, independently
+ of this flag.
You can specify extra mail header lines to be added to each message