Man page 1 : git-diff-tree

git-diff-tree - Compares the content and mode of blobs found via two tree objects

Compares the content and mode of the blobs found via two tree objects.

If there is only one <tree-ish> given, the commit is compared with its parents (see --stdin below).

Note that git diff-tree can use the tree encapsulated in a commit object.

-p, -u, --patch
    Generate patch (see section on generating patches).

-U<n>, --unified=<n>
    Generate diffs with <n> lines of context instead of the usual three. Implies -p.

--raw
    Generate the raw format. This is the default.

--patch-with-raw
    Synonym for -p --raw.

--patience
    Generate a diff using the "patience diff" algorithm.

--stat[=width[,name-width]]
    Generate a diffstat. You can override the default output width for 80-column terminal by --stat=width. The width of the filename part can be controlled by giving another width to it separated by a comma.

--numstat
    Similar to --stat, but shows number of added and deleted lines in decimal notation and pathname without abbreviation, to make it more machine friendly. For binary files, outputs two - instead of saying 0 0.

--shortstat
    Output only the last line of the --stat format containing total number of modified files, as well as number of added and deleted lines.

--dirstat[=limit]
    Output the distribution of relative amount of changes (number of lines added or removed) for each sub-directory. Directories with changes below a cut-off percent (3% by default) are not shown. The cut-off percent can be set with --dirstat=limit. Changes in a child directory is not counted for the parent directory, unless --cumulative is used.

--dirstat-by-file[=limit]
    Same as --dirstat, but counts changed files instead of lines.

--summary
    Output a condensed summary of extended header information such as creations, renames and mode changes.

--patch-with-stat
    Synonym for -p --stat.

-z
    When --raw, --numstat, --name-only or --name-status has been given, do not munge pathnames and use NULs as output field terminators.

Without this option, each pathname output will have TAB, LF, double quotes, and backslash characters replaced with \t, \n, \", and \\, respectively, and the pathname will be enclosed in double quotes if any of those replacements occurred.

--name-only
    Show only names of changed files.

--name-status
    Show only names and status of changed files. See the description of the --diff-filter option on what the status letters mean.

--submodule[=<format>]
    Chose the output format for submodule differences. <format> can be one of short and log. short just shows pairs of commit names, this format is used when this option is not given. log is the default value for this option and lists the commits in that commit range like the summary option of git-submodule(1) does.

--color[=<when>]
    Show colored diff. The value must be always (the default), never, or auto.

--no-color
    Turn off colored diff, even when the configuration file gives the default to color output. Same as --color=never.

--word-diff[=<mode>]
    Show a word diff, using the <mode> to delimit changed words. By default, words are delimited by whitespace; see --word-diff-regex below. The <mode> defaults to plain, and must be one of:

color
    Highlight changed words using only colors. Implies --color.

plain
    Show words as [-removed-] and {added}. Makes no attempts to escape the delimiters if they appear in the input, so the output may be ambiguous.

porcelain
    Use a special line-based format intended for script consumption. Added/removed/unchanged runs are printed in the usual unified diff format, starting with a +/-/` ` character at the beginning of the line and extending to the end of the line. Newlines in the input are represented by a tilde ~ on a line of its own.

none
    Disable word diff again.

Note that despite the name of the first mode, color is used to highlight the changed parts in all modes if enabled.

--word-diff-regex=<regex>
    Use <regex> to decide what a word is, instead of considering runs of non-whitespace to be a word. Also implies --word-diff unless it was already enabled.

Every non-overlapping match of the <regex> is considered a word. Anything between these matches is considered whitespace and ignored(!) for the purposes of finding differences. You may want to append |[^[:space:]] to your regular expression to make sure that it matches all non-whitespace characters. A match that contains a newline is silently truncated(!) at the newline.

The regex can also be set via a diff driver or configuration option, see gitattributes(1) or git-config(1). Giving it explicitly overrides any diff driver or configuration setting. Diff drivers override configuration settings.

--color-words[=<regex>]
    Equivalent to --word-diff=color plus (if a regex was specified) --word-diff-regex=<regex>.

--no-renames
    Turn off rename detection, even when the configuration file gives the default to do so.

--check
    Warn if changes introduce trailing whitespace or an indent that uses a space before a tab. Exits with non-zero status if problems are found. Not compatible with --exit-code.

--full-index
    Instead of the first handful of characters, show the full pre- and post-image blob object names on the "index" line when generating patch format output.

--binary
    In addition to --full-index, output a binary diff that can be applied with git-apply.

--abbrev[=<n>]
    Instead of showing the full 40-byte hexadecimal object name in diff-raw format output and diff-tree header lines, show only a partial prefix. This is independent of the --full-index option above, which controls the diff-patch output format. Non default number of digits can be specified with --abbrev=<n>.

-B[<n>][/<m>]
    Break complete rewrite changes into pairs of delete and create. This serves two purposes:

It affects the way a change that amounts to a total rewrite of a file not as a series of deletion and insertion mixed together with a very few lines that happen to match textually as the context, but as a single deletion of everything old followed by a single insertion of everything new, and the number m controls this aspect of the -B option (defaults to 60%). -B/70% specifies that less than 30% of the original should remain in the result for git to consider it a total rewrite (i.e. otherwise the resulting patch will be a series of deletion and insertion mixed together with context lines).

When used with -M, a totally-rewritten file is also considered as the source of a rename (usually -M only considers a file that disappeared as the source of a rename), and the number n controls this aspect of the -B option (defaults to 50%). -B20% specifies that a change with addition and deletion compared to 20% or more of the file(cqs size are eligible for being picked up as a possible source of a rename to another file.

-M[<n>]
    Detect renames. If n is specified, it is a is a threshold on the similarity index (i.e. amount of addition/deletions compared to the file(cqs size). For example, -M90% means git should consider a delete/add pair to be a rename if more than 90% of the file hasn(cqt changed.

-C[<n>]
    Detect copies as well as renames. See also --find-copies-harder. If n is specified, it has the same meaning as for -M<n>.

--diff-filter=[ACDMRTUXB*]
    Select only files that are Added (A), Copied (C), Deleted (D), Modified (M), Renamed (R), have their type (i.e. regular file, symlink, submodule, ...) changed (T), are Unmerged (U), are Unknown (X), or have had their pairing Broken (B). Any combination of the filter characters may be used. When * (All-or-none) is added to the combination, all paths are selected if there is any file that matches other criteria in the comparison; if there is no file that matches other criteria, nothing is selected.

--find-copies-harder
    For performance reasons, by default, -C option finds copies only if the original file of the copy was modified in the same changeset. This flag makes the command inspect unmodified files as candidates for the source of copy. This is a very expensive operation for large projects, so use it with caution. Giving more than one -C option has the same effect.

-l<num>
    The -M and -C options require O(n^2) processing time where n is the number of potential rename/copy targets. This option prevents rename/copy detection from running if the number of rename/copy targets exceeds the specified number.

-S<string>
    Look for differences that introduce or remove an instance of <string>. Note that this is different than the string simply appearing in diff output; see the pickaxe entry in gitdiffcore(7) for more details.

--pickaxe-all
    When -S finds a change, show all the changes in that changeset, not just the files that contain the change in <string>.

--pickaxe-regex
    Make the <string> not a plain string but an extended POSIX regex to match.

-O<orderfile>
    Output the patch in the order specified in the <orderfile>, which has one shell glob pattern per line.

-R
    Swap two inputs; that is, show differences from index or on-disk file to tree contents.

--relative[=<path>]
    When run from a subdirectory of the project, it can be told to exclude changes outside the directory and show pathnames relative to it with this option. When you are not in a subdirectory (e.g. in a bare repository), you can name which subdirectory to make the output relative to by giving a <path> as an argument.

-a, --text
    Treat all files as text.

--ignore-space-at-eol
    Ignore changes in whitespace at EOL.

-b, --ignore-space-change
    Ignore changes in amount of whitespace. This ignores whitespace at line end, and considers all other sequences of one or more whitespace characters to be equivalent.

-w, --ignore-all-space
    Ignore whitespace when comparing lines. This ignores differences even if one line has whitespace where the other line has none.

--inter-hunk-context=<lines>
    Show the context between diff hunks, up to the specified number of lines, thereby fusing hunks that are close to each other.

--exit-code
    Make the program exit with codes similar to diff(1). That is, it exits with 1 if there were differences and 0 means no differences.

--quiet
    Disable all output of the program. Implies --exit-code.

--ext-diff
    Allow an external diff helper to be executed. If you set an external diff driver with gitattributes(5), you need to use this option with git-log(1) and friends.

--no-ext-diff
    Disallow external diff drivers.

--ignore-submodules[=<when>]
    Ignore changes to submodules in the diff generation. <when> can be either "untracked", "dirty" or "all", which is the default. When "untracked" is used submodules are not considered dirty when they only contain untracked content (but they are still scanned for modified content). Using "dirty" ignores all changes to the work tree of submodules, only changes to the commits stored in the superproject are shown (this was the behavior until 1.7.0). Using "all" hides all changes to submodules.

--src-prefix=<prefix>
    Show the given source prefix instead of "a/".

--dst-prefix=<prefix>
    Show the given destination prefix instead of "b/".

--no-prefix
    Do not show any source or destination prefix.

For more detailed explanation on these common options, see also gitdiffcore(7).

<tree-ish>
    The id of a tree object.

<path>...
    If provided, the results are limited to a subset of files matching one of these prefix strings. i.e., file matches /^<pattern1>|<pattern2>|.../ Note that this parameter does not provide any wildcard or regexp features.

-r
    recurse into sub-trees

-t
    show tree entry itself as well as subtrees. Implies -r.

--root
    When --root is specified the initial commit will be shown as a big creation event. This is equivalent to a diff against the NULL tree.

--stdin
    When --stdin is specified, the command does not take <tree-ish> arguments from the command line. Instead, it reads lines containing either two <tree>, one <commit>, or a list of <commit> from its standard input. (Use a single space as separator.)

When two trees are given, it compares the first tree with the second. When a single commit is given, it compares the commit with its parents. The remaining commits, when given, are used as if they are parents of the first commit.

When comparing two trees, the ID of both trees (separated by a space and terminated by a newline) is printed before the difference. When comparing commits, the ID of the first (or only) commit, followed by a newline, is printed.

The following flags further affect the behavior when comparing commits (but not trees).

-m
    By default, git diff-tree --stdin does not show differences for merge commits. With this flag, it shows differences to that commit from all of its parents. See also -c.

-s
    By default, git diff-tree --stdin shows differences, either in machine-readable form (without -p) or in patch form (with -p). This output can be suppressed. It is only useful with -v flag.

-v
    This flag causes git diff-tree --stdin to also show the commit message before the differences.

--pretty[=<format>], --format=<format>
    Pretty-print the contents of the commit logs in a given format, where <format> can be one of oneline, short, medium, full, fuller, email, raw and format:<string>. See the "PRETTY FORMATS" section for some additional details for each format. When omitted, the format defaults to medium.

Note: you can specify the default pretty format in the repository configuration (see git-config(1)).

--abbrev-commit
    Instead of showing the full 40-byte hexadecimal commit object name, show only a partial prefix. Non default number of digits can be specified with "--abbrev=<n>" (which also modifies diff output, if it is displayed).

This should make "--pretty=oneline" a whole lot more readable for people using 80-column terminals.

--oneline
    This is a shorthand for "--pretty=oneline --abbrev-commit" used together.

--encoding[=<encoding>]
    The commit objects record the encoding used for the log message in their encoding header; this option can be used to tell the command to re-code the commit log message in the encoding preferred by the user. For non plumbing commands this defaults to UTF-8.

--no-notes, --show-notes[=<ref>]
    Show the notes (see git-notes(1)) that annotate the commit, when showing the commit log message. This is the default for git log, git show and git whatchanged commands when there is no --pretty, --format nor --oneline option is given on the command line.

With an optional argument, add this ref to the list of notes. The ref is taken to be in refs/notes/ if it is not qualified.

--[no-]standard-notes
    Enable or disable populating the notes ref list from the core.notesRef and notes.displayRef variables (or corresponding environment overrides). Enabled by default. See git-config(1).

--no-commit-id
     git diff-tree outputs a line with the commit ID when applicable. This flag suppressed the commit ID output.

-c
    This flag changes the way a merge commit is displayed (which means it is useful only when the command is given one <tree-ish>, or --stdin). It shows the differences from each of the parents to the merge result simultaneously instead of showing pairwise diff between a parent and the result one at a time (which is what the -m option does). Furthermore, it lists only files which were modified from all parents.

--cc
    This flag changes the way a merge commit patch is displayed, in a similar way to the -c option. It implies the -c and -p options and further compresses the patch output by omitting uninteresting hunks whose the contents in the parents have only two variants and the merge result picks one of them without modification. When all hunks are uninteresting, the commit itself and the commit log message is not shown, just like in any other "empty diff" case.

--always
    Show the commit itself and the commit log message even if the diff itself is empty.

If the commit is a merge, and if the pretty-format is not oneline, email or raw, an additional line is inserted before the Author: line. This line begins with "Merge: " and the sha1s of ancestral commits are printed, separated by spaces. Note that the listed commits may not necessarily be the list of the direct parent commits if you have limited your view of history: for example, if you are only interested in changes related to a certain directory or file.

There are several built-in formats, and you can define additional formats by setting a pretty.<name> config option to either another format name, or a format: string, as described below (see git-config(1)). Here are the details of the built-in formats:


    .ie n \ \h'-04'\h'+03'\c .

2.3 . oneline


    .

<sha1> <title line>

.

This is designed to be as compact as possible.


    .ie n \ \h'-04'\h'+03'\c .

2.3 . short


    .

commit <sha1>
Author: <author>

.


    .

<title line>

.


    .ie n \ \h'-04'\h'+03'\c .

2.3 . medium


    .

commit <sha1>
Author: <author>
Date:   <author date>

.


    .

<title line>

.


    .

<full commit message>

.


    .ie n \ \h'-04'\h'+03'\c .

2.3 . full


    .

commit <sha1>
Author: <author>
Commit: <committer>

.


    .

<title line>

.


    .

<full commit message>

.


    .ie n \ \h'-04'\h'+03'\c .

2.3 . fuller


    .

commit <sha1>
Author:     <author>
AuthorDate: <author date>
Commit:     <committer>
CommitDate: <committer date>

.


    .

<title line>

.


    .

<full commit message>

.


    .ie n \ \h'-04'\h'+03'\c .

2.3 . email


    .

From <sha1> <date>
From: <author>
Date: <author date>
Subject: [PATCH] <title line>

.


    .

<full commit message>

.


    .ie n \ \h'-04'\h'+03'\c .

2.3 . raw

The raw format shows the entire commit exactly as stored in the commit object. Notably, the SHA1s are displayed in full, regardless of whether --abbrev or --no-abbrev are used, and parents information show the true parent commits, without taking grafts nor history simplification into account.


    .ie n \ \h'-04'\h'+03'\c .

2.3 . format:<string>

The format:<string> format allows you to specify which information you want to show. It works a little bit like printf format, with the notable exception that you get a newline with %n instead of \n.

E.g, format:"The author of %h was %an, %ar%nThe title was >>%s<<%n" would show something like this:


    .

The author of fe6e0ee was Junio C Hamano, 23 hours ago
The title was >>t4119: test autocomputing -p<n> for traditional diff input.<<

.

The placeholders are:


    .ie n \ \h'-04'\h'+03'\c .

2.3 . %H: commit hash


    .ie n \ \h'-04'\h'+03'\c .

2.3 . %h: abbreviated commit hash


    .ie n \ \h'-04'\h'+03'\c .

2.3 . %T: tree hash


    .ie n \ \h'-04'\h'+03'\c .

2.3 . %t: abbreviated tree hash


    .ie n \ \h'-04'\h'+03'\c .

2.3 . %P: parent hashes


    .ie n \ \h'-04'\h'+03'\c .

2.3 . %p: abbreviated parent hashes


    .ie n \ \h'-04'\h'+03'\c .

2.3 . %an: author name


    .ie n \ \h'-04'\h'+03'\c .

2.3 . %aN: author name (respecting .mailmap, see git-shortlog(1) or git-blame(1))


    .ie n \ \h'-04'\h'+03'\c .

2.3 . %ae: author email


    .ie n \ \h'-04'\h'+03'\c .

2.3 . %aE: author email (respecting .mailmap, see git-shortlog(1) or git-blame(1))


    .ie n \ \h'-04'\h'+03'\c .

2.3 . %ad: author date (format respects --date= option)


    .ie n \ \h'-04'\h'+03'\c .

2.3 . %aD: author date, RFC2822 style


    .ie n \ \h'-04'\h'+03'\c .

2.3 . %ar: author date, relative


    .ie n \ \h'-04'\h'+03'\c .

2.3 . %at: author date, UNIX timestamp


    .ie n \ \h'-04'\h'+03'\c .

2.3 . %ai: author date, ISO 8601 format


    .ie n \ \h'-04'\h'+03'\c .

2.3 . %cn: committer name


    .ie n \ \h'-04'\h'+03'\c .

2.3 . %cN: committer name (respecting .mailmap, see git-shortlog(1) or git-blame(1))


    .ie n \ \h'-04'\h'+03'\c .

2.3 . %ce: committer email


    .ie n \ \h'-04'\h'+03'\c .

2.3 . %cE: committer email (respecting .mailmap, see git-shortlog(1) or git-blame(1))


    .ie n \ \h'-04'\h'+03'\c .

2.3 . %cd: committer date


    .ie n \ \h'-04'\h'+03'\c .

2.3 . %cD: committer date, RFC2822 style


    .ie n \ \h'-04'\h'+03'\c .

2.3 . %cr: committer date, relative


    .ie n \ \h'-04'\h'+03'\c .

2.3 . %ct: committer date, UNIX timestamp


    .ie n \ \h'-04'\h'+03'\c .

2.3 . %ci: committer date, ISO 8601 format


    .ie n \ \h'-04'\h'+03'\c .

2.3 . %d: ref names, like the --decorate option of git-log(1)


    .ie n \ \h'-04'\h'+03'\c .

2.3 . %e: encoding


    .ie n \ \h'-04'\h'+03'\c .

2.3 . %s: subject


    .ie n \ \h'-04'\h'+03'\c .

2.3 . %f: sanitized subject line, suitable for a filename


    .ie n \ \h'-04'\h'+03'\c .

2.3 . %b: body


    .ie n \ \h'-04'\h'+03'\c .

2.3 . %B: raw body (unwrapped subject and body)


    .ie n \ \h'-04'\h'+03'\c .

2.3 . %N: commit notes


    .ie n \ \h'-04'\h'+03'\c .

2.3 . %gD: reflog selector, e.g.,


    .ie n \ \h'-04'\h'+03'\c .

2.3 . %gd: shortened reflog selector, e.g.,


    .ie n \ \h'-04'\h'+03'\c .

2.3 . %gs: reflog subject


    .ie n \ \h'-04'\h'+03'\c .

2.3 . %Cred: switch color to red


    .ie n \ \h'-04'\h'+03'\c .

2.3 . %Cgreen: switch color to green


    .ie n \ \h'-04'\h'+03'\c .

2.3 . %Cblue: switch color to blue


    .ie n \ \h'-04'\h'+03'\c .

2.3 . %Creset: reset color


    .ie n \ \h'-04'\h'+03'\c .

2.3 . %C(...): color specification, as described in color
anch.* config option


    .ie n \ \h'-04'\h'+03'\c .

2.3 . %m: left, right or boundary mark


    .ie n \ \h'-04'\h'+03'\c .

2.3 . %n: newline


    .ie n \ \h'-04'\h'+03'\c .

2.3 . %%: a raw %


    .ie n \ \h'-04'\h'+03'\c .

2.3 . %x00: print a byte from a hex code


    .ie n \ \h'-04'\h'+03'\c .

2.3 . %w([<w>[,<i1>[,<i2>]]]): switch line wrapping, like the -w option of git-shortlog(1).

.
    .it 1 an-trap
.ps +1 Note .ps -1


Some placeholders may depend on other options given to the revision traversal engine. For example, the %g* reflog options will insert an empty string unless we are traversing reflog entries (e.g., by git log -g). The %d placeholder will use the "short" decoration format if --decorate was not already provided on the command line.



If you add a + (plus sign) after % of a placeholder, a line-feed is inserted immediately before the expansion if and only if the placeholder expands to a non-empty string.

If you add a - (minus sign) after % of a placeholder, line-feeds that immediately precede the expansion are deleted if and only if the placeholder expands to an empty string.

If you add a ` ` (space) after % of a placeholder, a space is inserted immediately before the expansion if and only if the placeholder expands to a non-empty string.


    .ie n \ \h'-04'\h'+03'\c .

2.3 . tformat:

The tformat: format works exactly like format:, except that it provides "terminator" semantics instead of "separator" semantics. In other words, each commit has the message terminator character (usually a newline) appended, rather than a separator placed between entries. This means that the final entry of a single-line format will be properly terminated with a new line, just as the "oneline" format does. For example:


    .

$ git log -2 --pretty=format:%h 4da45bef \
  | perl -pe \*(Aq$_ .= " -- NO NEWLINE\n" unless /\n/\*(Aq
4da45be
7134973 -- NO NEWLINE
$ git log -2 --pretty=tformat:%h 4da45bef \
  | perl -pe \*(Aq$_ .= " -- NO NEWLINE\n" unless /\n/\*(Aq
4da45be
7134973

.

In addition, any unrecognized string that has a % in it is interpreted as if it has tformat: in front of it. For example, these two are equivalent:


    .

$ git log -2 --pretty=tformat:%h 4da45bef
$ git log -2 --pretty=%h 4da45bef

.

If you(cqre only interested in differences in a subset of files, for example some architecture-specific files, you might do:


    .

git diff-tree -r <tree-ish> <tree-ish> arch/ia64 include/asm-ia64

.

and it will only show you what changed in those two directories.

Or if you are searching for what changed in just kernel/sched.c, just do


    .

git diff-tree -r <tree-ish> <tree-ish> kernel/sched.c

.

and it will ignore all differences to other files.

The pattern is always the prefix, and is matched exactly. There are no wildcards. Even stricter, it has to match a complete path component. I.e. "foo" does not pick up foobar.h. "foo" does match foo/bar.h so it can be used to name subdirectories.

An example of normal usage is:


    .

torvalds@ppc970:~/git> git diff-tree 5319e4......
*100664->100664 blob    ac348b.......->a01513.......      git-fsck-objects.c

.

which tells you that the last commit changed just one file (it(cqs from this one:


    .

commit 3c6f7ca19ad4043e9e72fa94106f352897e651a8
tree 5319e4d609cdd282069cc4dce33c1db559539b03
parent b4e628ea30d5ab3606119d2ea5caeab141d38df7
author Linus Torvalds <torvalds@ppc970.osdl.org> Sat Apr 9 12:02:30 2005
committer Linus Torvalds <torvalds@ppc970.osdl.org> Sat Apr 9 12:02:30 2005
Make "git-fsck-objects" print out all the root commits it finds.
Once I do the reference tracking, I\*(Aqll also make it print out all the
HEAD commits it finds, which is even more interesting.

.



in case you care).

The raw output format from "git-diff-index", "git-diff-tree", "git-diff-files" and "git diff --raw" are very similar.

These commands all compare two sets of things; what is compared differs:

git-diff-index <tree-ish>
    compares the <tree-ish> and the files on the filesystem.

git-diff-index --cached <tree-ish>
    compares the <tree-ish> and the index.

git-diff-tree [-r] <tree-ish-1> <tree-ish-2> [<pattern>...]
    compares the trees named by the two arguments.

git-diff-files [<pattern>...]
    compares the index and the files on the filesystem.

The "git-diff-tree" command begins its output by printing the hash of what is being compared. After that, all the commands print one output line per changed file.

An output line is formatted this way:


    .

in-place edit  :100644 100644 bcd1234... 0123456... M file0
copy-edit      :100644 100644 abcd123... 1234567... C68 file1 file2
rename-edit    :100644 100644 abcd123... 1234567... R86 file1 file3
create         :000000 100644 0000000... 1234567... A file4
delete         :100644 000000 1234567... 0000000... D file5
unmerged       :000000 000000 0000000... 0000000... U file6

.



That is, from the left to the right:


    .ie n \ \h'-04' 1.\h'+01'\c .

1. 4.2 . a colon.


    .ie n \ \h'-04' 2.\h'+01'\c .

2. 4.2 . mode for "src"; 000000 if creation or unmerged.


    .ie n \ \h'-04' 3.\h'+01'\c .

3. 4.2 . a space.


    .ie n \ \h'-04' 4.\h'+01'\c .

4. 4.2 . mode for "dst"; 000000 if deletion or unmerged.


    .ie n \ \h'-04' 5.\h'+01'\c .

5. 4.2 . a space.


    .ie n \ \h'-04' 6.\h'+01'\c .

6. 4.2 . sha1 for "src"; 0{40} if creation or unmerged.


    .ie n \ \h'-04' 7.\h'+01'\c .

7. 4.2 . a space.


    .ie n \ \h'-04' 8.\h'+01'\c .

8. 4.2 . sha1 for "dst"; 0{40} if creation, unmerged or "look at work tree".


    .ie n \ \h'-04' 9.\h'+01'\c .

9. 4.2 . a space.


    .ie n \ \h'-04'10.\h'+01'\c .

10. 4.2 . status, followed by optional "score" number.


    .ie n \ \h'-04'11.\h'+01'\c .

11. 4.2 . a tab or a NUL when -z option is used.


    .ie n \ \h'-04'12.\h'+01'\c .

12. 4.2 . path for "src"


    .ie n \ \h'-04'13.\h'+01'\c .

13. 4.2 . a tab or a NUL when -z option is used; only exists for C or R.


    .ie n \ \h'-04'14.\h'+01'\c .

14. 4.2 . path for "dst"; only exists for C or R.


    .ie n \ \h'-04'15.\h'+01'\c .

15. 4.2 . an LF or a NUL when -z option is used, to terminate the record.

Possible status letters are:


    .ie n \ \h'-04'\h'+03'\c .

2.3 . A: addition of a file


    .ie n \ \h'-04'\h'+03'\c .

2.3 . C: copy of a file into a new one


    .ie n \ \h'-04'\h'+03'\c .

2.3 . D: deletion of a file


    .ie n \ \h'-04'\h'+03'\c .

2.3 . M: modification of the contents or mode of a file


    .ie n \ \h'-04'\h'+03'\c .

2.3 . R: renaming of a file


    .ie n \ \h'-04'\h'+03'\c .

2.3 . T: change in the type of the file


    .ie n \ \h'-04'\h'+03'\c .

2.3 . U: file is unmerged (you must complete the merge before it can be committed)


    .ie n \ \h'-04'\h'+03'\c .

2.3 . X: "unknown" change type (most probably a bug, please report it)

Status letters C and R are always followed by a score (denoting the percentage of similarity between the source and target of the move or copy), and are the only ones to be so.

<sha1> is shown as all 0(cqs if a file is new on the filesystem and it is out of sync with the index.

Example:


    .

:100644 100644 5be4a4...... 000000...... M file.c

.



When -z option is not used, TAB, LF, and backslash characters in pathnames are represented as \t, \n, and \\, respectively.

"git-diff-tree", "git-diff-files" and "git-diff --raw" can take -c or --cc option to generate diff output also for merge commits. The output differs from the format described above in the following way:


    .ie n \ \h'-04' 1.\h'+01'\c .

1. 4.2 . there is a colon for each parent


    .ie n \ \h'-04' 2.\h'+01'\c .

2. 4.2 . there are more "src" modes and "src" sha1


    .ie n \ \h'-04' 3.\h'+01'\c .

3. 4.2 . status is concatenated status characters for each parent


    .ie n \ \h'-04' 4.\h'+01'\c .

4. 4.2 . no optional "score" number


    .ie n \ \h'-04' 5.\h'+01'\c .

5. 4.2 . single path, only for "dst"

Example:


    .

::100644 100644 100644 fabadb8... cc95eb0... 4866510... MM      describe.c

.



Note that combined diff lists only files which were modified from all parents.

When "git-diff-index", "git-diff-tree", or "git-diff-files" are run with a -p option, "git diff" without the --raw option, or "git log" with the "-p" option, they do not produce the output described above; instead they produce a patch file. You can customize the creation of such patches via the GIT_EXTERNAL_DIFF and the GIT_DIFF_OPTS environment variables.

What the -p option produces is slightly different from the traditional diff format.


    .ie n \ \h'-04' 1.\h'+01'\c .

1. 4.2 . It is preceded with a "git diff" header, that looks like this:


    .

diff --git a/file1 b/file2

.

The a/ and b/ filenames are the same unless rename/copy is involved. Especially, even for a creation or a deletion, /dev/null is not used in place of a/ or b/ filenames.

When rename/copy is involved, file1 and file2 show the name of the source file of the rename/copy and the name of the file that rename/copy produces, respectively.


    .ie n \ \h'-04' 2.\h'+01'\c .

2. 4.2 . It is followed by one or more extended header lines:


    .

old mode <mode>
new mode <mode>
deleted file mode <mode>
new file mode <mode>
copy from <path>
copy to <path>
rename from <path>
rename to <path>
similarity index <number>
dissimilarity index <number>
index <hash>..<hash> <mode>

.


    .ie n \ \h'-04' 3.\h'+01'\c .

3. 4.2 . TAB, LF, double quote and backslash characters in pathnames are represented as \t, \n, \" and \\, respectively. If there is need for such substitution then the whole pathname is put in double quotes.

The similarity index is the percentage of unchanged lines, and the dissimilarity index is the percentage of changed lines. It is a rounded down integer, followed by a percent sign. The similarity index value of 100% is thus reserved for two equal files, while 100% dissimilarity means that no line from the old file made it into the new one.

"git-diff-tree", "git-diff-files" and "git-diff" can take -c or --cc option to produce combined diff. For showing a merge commit with "git log -p", this is the default format; you can force showing full diff with the -m option. A combined diff format looks like this:


    .

diff --combined describe.c
index fabadb8,cc95eb0..4866510
--- a/describe.c
+++ b/describe.c
@@@ -98,20 -98,12 +98,20 @@@
        return (a_date > b_date) ? -1 : (a_date == b_date) ? 0 : 1;
  }
- static void describe(char *arg)
 -static void describe(struct commit *cmit, int last_one)
++static void describe(char *arg, int last_one)
  {
 +      unsigned char sha1[20];
 +      struct commit *cmit;
        struct commit_list *list;
        static int initialized = 0;
        struct commit_name *n;
 +      if (get_sha1(arg, sha1) < 0)
 +              usage(describe_usage);
 +      cmit = lookup_commit_reference(sha1);
 +      if (!cmit)
 +              usage(describe_usage);
 +
        if (!initialized) {
                initialized = 1;
                for_each_ref(get_name);

.




    .ie n \ \h'-04' 1.\h'+01'\c .

1. 4.2 . It is preceded with a "git diff" header, that looks like this (when -c option is used):


    .

diff --combined file

.

or like this (when --cc option is used):


    .

diff --cc file

.


    .ie n \ \h'-04' 2.\h'+01'\c .

2. 4.2 . It is followed by one or more extended header lines (this example shows a merge with two parents):


    .

index <hash>,<hash>..<hash>
mode <mode>,<mode>..<mode>
new file mode <mode>
deleted file mode <mode>,<mode>

.

The mode <mode>,<mode>..<mode> line appears only if at least one of the <mode> is different from the rest. Extended headers with information about detected contents movement (renames and copying detection) are designed to work with diff of two <tree-ish> and are not used by combined diff format.


    .ie n \ \h'-04' 3.\h'+01'\c .

3. 4.2 . It is followed by two-line from-file/to-file header


    .

--- a/file
+++ b/file

.

Similar to two-line header for traditional unified diff format, /dev/null is used to signal created or deleted files.


    .ie n \ \h'-04' 4.\h'+01'\c .

4. 4.2 . Chunk header format is modified to prevent people from accidentally feeding it to patch -p1. Combined diff format was created for review of merge commit changes, and was not meant for apply. The change is similar to the change in the extended index header:


    .

@@@ <from-file-range> <from-file-range> <to-file-range> @@@

.

There are (number of parents + 1) @ characters in the chunk header for combined diff format.

Unlike the traditional unified diff format, which shows two files A and B with a single column that has - (minus appears in A but removed in B), + (plus missing in A but added to B), or " " (space unchanged) prefix, this format compares two or more files file1, file2,... with one file X, and shows how X differs from each of fileN. One column for each of fileN is prepended to the output line to note how X(cqs line is different from it.

A - character in the column N means that the line appears in fileN but it does not appear in the result. A + character in the column N means that the line appears in the result, and fileN does not have that line (in other words, the line was added, from the point of view of that parent).

In the above example output, the function signature was changed from both files (hence two - removals from both file1 and file2, plus ++ to mean one line that was added does not appear in either file1 nor file2). Also eight other lines are the same from file1 but do not appear in file2 (hence prefixed with +).

When shown by git diff-tree -c, it compares the parents of a merge commit with the merge result (i.e. file1..fileN are the parents). When shown by git diff-files -c, it compares the two unresolved merge parents with the working tree file (i.e. file1 is stage 2 aka "our version", file2 is stage 3 aka "their version").

The --summary option describes newly added, deleted, renamed and copied files. The --stat option adds diffstat(1) graph to the output. These options can be combined with other options, such as -p, and are meant for human consumption.

When showing a change that involves a rename or a copy, --stat output formats the pathnames compactly by combining common prefix and suffix of the pathnames. For example, a change that moves arch/i386/Makefile to arch/x86/Makefile while modifying 4 lines will be shown like this:


    .

arch/{i386 => x86}/Makefile    |   4 +--

.



The --numstat option gives the diffstat(1) information but is designed for easier machine consumption. An entry in --numstat output looks like this:


    .

1       2       README
3       1       arch/{i386 => x86}/Makefile

.



That is, from left to right:


    .ie n \ \h'-04' 1.\h'+01'\c .

1. 4.2 . the number of added lines;


    .ie n \ \h'-04' 2.\h'+01'\c .

2. 4.2 . a tab;


    .ie n \ \h'-04' 3.\h'+01'\c .

3. 4.2 . the number of deleted lines;


    .ie n \ \h'-04' 4.\h'+01'\c .

4. 4.2 . a tab;


    .ie n \ \h'-04' 5.\h'+01'\c .

5. 4.2 . pathname (possibly with rename/copy information);


    .ie n \ \h'-04' 6.\h'+01'\c .

6. 4.2 . a newline.

When -z output option is in effect, the output is formatted this way:


    .

1       2       README NUL
3       1       NUL arch/i386/Makefile NUL arch/x86/Makefile NUL

.



That is:


    .ie n \ \h'-04' 1.\h'+01'\c .

1. 4.2 . the number of added lines;


    .ie n \ \h'-04' 2.\h'+01'\c .

2. 4.2 . a tab;


    .ie n \ \h'-04' 3.\h'+01'\c .

3. 4.2 . the number of deleted lines;


    .ie n \ \h'-04' 4.\h'+01'\c .

4. 4.2 . a tab;


    .ie n \ \h'-04' 5.\h'+01'\c .

5. 4.2 . a NUL (only exists if renamed/copied);


    .ie n \ \h'-04' 6.\h'+01'\c .

6. 4.2 . pathname in preimage;


    .ie n \ \h'-04' 7.\h'+01'\c .

7. 4.2 . a NUL (only exists if renamed/copied);


    .ie n \ \h'-04' 8.\h'+01'\c .

8. 4.2 . pathname in postimage (only exists if renamed/copied);


    .ie n \ \h'-04' 9.\h'+01'\c .

9. 4.2 . a NUL.

The extra NUL before the preimage path in renamed case is to allow scripts that read the output to tell if the current record being read is a single-path record or a rename/copy record without reading ahead. After reading added and deleted lines, reading up to NUL would yield the pathname, but if that is NUL, the record will show two paths.

Written by Linus Torvalds <\m[blue]\\fR\m[]\s-2\u[1]\d\s+2>

Documentation by David Greaves, Junio C Hamano and the git-list <\m[blue]\\fR\m[]\s-2\u[2]\d\s+2>.

Part of the git(1) suite

1. 4
    mailto:

2. 4
    mailto: