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