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.
33
44These commands all compare two sets of things; what is
55compared differs:
@@ -62,7 +62,8 @@ respectively.
6262diff format for merges
6363----------------------
6464
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
6667to generate diff output also for merge commits. The output differs
6768from the format described above in the following way:
6869
@@ -86,10 +87,10 @@ Generating patches with -p
8687--------------------------
8788
8889When "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.
9394
9495What the -p option produces is slightly different from the traditional
9596diff format.
@@ -137,8 +138,8 @@ file made it into the new one.
137138combined diff format
138139--------------------
139140
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:
142143
143144------------
144145diff --combined describe.c
0 commit comments