7 git-diff-tree - Compares the content and mode of blobs found via two tree objects
12 'git-diff-tree' [--stdin] [-m] [-s] [-v] [--pretty] [-t] [<common diff options>] <tree-ish> [<tree-ish>] [<path>...]
16 Compares the content and mode of the blobs found via two tree objects.
18 If there is only one <tree-ish> given, the commit is compared with its parents
21 Note that "git-diff-tree" can use the tree encapsulated in a commit object.
25 include::diff-options.txt[]
28 The id of a tree object.
31 If provided, the results are limited to a subset of files
32 matching one of these prefix strings.
33 ie file matches `/^<pattern1>|<pattern2>|.../`
34 Note that this parameter does not provide any wildcard or regexp
38 show tree entry itself as well as subtrees. Implies -r.
41 When '--root' is specified the initial commit will be showed as a big
42 creation event. This is equivalent to a diff against the NULL tree.
45 When '--stdin' is specified, the command does not take
46 <tree-ish> arguments from the command line. Instead, it
47 reads either one <commit> or a pair of <tree-ish>
48 separated with a single space from its standard input.
50 When a single commit is given on one line of such input, it compares
51 the commit with its parents. The following flags further affects its
52 behaviour. This does not apply to the case where two <tree-ish>
53 separated with a single space are given.
56 By default, "git-diff-tree --stdin" does not show
57 differences for merge commits. With this flag, it shows
58 differences to that commit from all of its parents.
61 By default, "git-diff-tree --stdin" shows differences,
62 either in machine-readable form (without '-p') or in patch
63 form (with '-p'). This output can be supressed. It is
64 only useful with '-v' flag.
67 This flag causes "git-diff-tree --stdin" to also show
68 the commit message before the differences.
70 --pretty[=(raw|medium|short)]::
71 This is used to control "pretty printing" format of the
72 commit message. Without "=<style>", it defaults to
78 If you're only interested in differences in a subset of files, for
79 example some architecture-specific files, you might do:
81 git-diff-tree -r <tree-ish> <tree-ish> arch/ia64 include/asm-ia64
83 and it will only show you what changed in those two directories.
85 Or if you are searching for what changed in just `kernel/sched.c`, just do
87 git-diff-tree -r <tree-ish> <tree-ish> kernel/sched.c
89 and it will ignore all differences to other files.
91 The pattern is always the prefix, and is matched exactly. There are no
92 wildcards. Even stricter, it has to match a complete path component.
93 I.e. "foo" does not pick up `foobar.h`. "foo" does match `foo/bar.h`
94 so it can be used to name subdirectories.
96 An example of normal usage is:
98 torvalds@ppc970:~/git> git-diff-tree 5319e4......
99 *100664->100664 blob ac348b.......->a01513....... git-fsck-objects.c
101 which tells you that the last commit changed just one file (it's from
104 -----------------------------------------------------------------------------
105 commit 3c6f7ca19ad4043e9e72fa94106f352897e651a8
106 tree 5319e4d609cdd282069cc4dce33c1db559539b03
107 parent b4e628ea30d5ab3606119d2ea5caeab141d38df7
108 author Linus Torvalds <torvalds@ppc970.osdl.org> Sat Apr 9 12:02:30 2005
109 committer Linus Torvalds <torvalds@ppc970.osdl.org> Sat Apr 9 12:02:30 2005
111 Make "git-fsck-objects" print out all the root commits it finds.
113 Once I do the reference tracking, I'll also make it print out all the
114 HEAD commits it finds, which is even more interesting.
115 -----------------------------------------------------------------------------
121 include::diff-format.txt[]
126 Written by Linus Torvalds <torvalds@osdl.org>
130 Documentation by David Greaves, Junio C Hamano and the git-list <git@vger.kernel.org>.
134 Part of the gitlink:git[7] suite