1
- The output format from "git-diff-index", "git-diff-tree" and
2
- "git-diff-files" are very similar.
1
+ The output format from "git-diff-index", "git-diff-tree",
2
+ "git-diff-files" and "git diff --raw" are very similar.
3
3
4
4
These commands all compare two sets of things; what is
5
5
compared differs:
@@ -62,7 +62,8 @@ respectively.
62
62
diff format for merges
63
63
----------------------
64
64
65
- "git-diff-tree" and "git-diff-files" can take '-c' or '--cc' option
65
+ "git-diff-tree", "git-diff-files" and "git-diff --raw"
66
+ can take '-c' or '--cc' option
66
67
to generate diff output also for merge commits. The output differs
67
68
from the format described above in the following way:
68
69
@@ -86,10 +87,10 @@ Generating patches with -p
86
87
--------------------------
87
88
88
89
When "git-diff-index", "git-diff-tree", or "git-diff-files" are run
89
- with a '-p' option, they do not produce the output described above;
90
- instead they produce a patch file. You can customize the creation
91
- of such patches via the GIT_EXTERNAL_DIFF and the GIT_DIFF_OPTS
92
- environment variables.
90
+ with a '-p' option, or "git diff" without the '--raw' option, they
91
+ do not produce the output described above; instead they produce a
92
+ patch file. You can customize the creation of such patches via the
93
+ GIT_EXTERNAL_DIFF and the GIT_DIFF_OPTS environment variables.
93
94
94
95
What the -p option produces is slightly different from the traditional
95
96
diff format.
@@ -137,8 +138,8 @@ file made it into the new one.
137
138
combined diff format
138
139
--------------------
139
140
140
- git-diff-tree and git-diff-files can take '-c' or '--cc' option
141
- to produce 'combined diff', which looks like this:
141
+ " git-diff-tree", " git-diff-files" and "git-diff" can take '-c' or
142
+ '--cc' option to produce 'combined diff', which looks like this:
142
143
143
144
------------
144
145
diff --combined describe.c
0 commit comments