1git-diff-tree(1) 2================ 3v0.1, May 2005 4 5NAME 6---- 7git-diff-tree - Compares the content and mode of blobs found via two tree objects 8 9 10SYNOPSIS 11-------- 12'git-diff-tree' [-p] [-r] [-z] [--stdin] [-M] [-m] [-s] [-v] <tree-ish> <tree-ish> [<pattern>]\* 13 14DESCRIPTION 15----------- 16Compares the content and mode of the blobs found via two tree objects. 17 18Note that "git-diff-tree" can use the tree encapsulated in a commit object. 19 20OPTIONS 21------- 22<tree-ish>:: 23 The id of a tree object. 24 25<pattern>:: 26 If provided, the results are limited to a subset of files 27 matching one of these prefix strings. 28 ie file matches `/^<pattern1>|<pattern2>|.../` 29 Note that pattern does not provide any wildcard or regexp 30 features. 31 32-p:: 33 generate patch (see section on generating patches). For 34 git-diff-tree, this flag implies '-r' as well. 35 36-M:: 37 Detect renames; implies -p, in turn implying also '-r'. 38 39-r:: 40 recurse 41 42-z:: 43 \0 line termination on output 44 45--stdin:: 46 When '--stdin' is specified, the command does not take 47 <tree-ish> arguments from the command line. Instead, it 48 reads either one <commit> or a pair of <tree-ish> 49 separated with a single space from its standard input. 50+ 51When a single commit is given on one line of such input, it compares 52the commit with its parents. The following flags further affects its 53behaviour. This does not apply to the case where two <tree-ish> 54separated with a single space are given. 55 56-m:: 57 By default, "git-diff-tree --stdin" does not show 58 differences for merge commits. With this flag, it shows 59 differences to that commit from all of its parents. 60 61-s:: 62 By default, "git-diff-tree --stdin" shows differences, 63 either in machine-readable form (without '-p') or in patch 64 form (with '-p'). This output can be supressed. It is 65 only useful with '-v' flag. 66 67-v:: 68 This flag causes "git-diff-tree --stdin" to also show 69 the commit message before the differences. 70 71 72Limiting Output 73--------------- 74If you're only interested in differences in a subset of files, for 75example some architecture-specific files, you might do: 76 77 git-diff-tree -r <tree-ish> <tree-ish> arch/ia64 include/asm-ia64 78 79and it will only show you what changed in those two directories. 80 81Or if you are searching for what changed in just `kernel/sched.c`, just do 82 83 git-diff-tree -r <tree-ish> <tree-ish> kernel/sched.c 84 85and it will ignore all differences to other files. 86 87The pattern is always the prefix, and is matched exactly. There are no 88wildcards. Even stricter, it has to match complete path comonent. 89I.e. "foo" does not pick up `foobar.h`. "foo" does match `foo/bar.h` 90so it can be used to name subdirectories. 91 92An example of normal usage is: 93 94 torvalds@ppc970:~/git> git-diff-tree 5319e4...... 95 *100664->100664 blob ac348b.......->a01513....... git-fsck-cache.c 96 97which tells you that the last commit changed just one file (it's from 98this one: 99 100 commit 3c6f7ca19ad4043e9e72fa94106f352897e651a8 101 tree 5319e4d609cdd282069cc4dce33c1db559539b03 102 parent b4e628ea30d5ab3606119d2ea5caeab141d38df7 103 author Linus Torvalds <torvalds@ppc970.osdl.org> Sat Apr 9 12:02:30 2005 104 committer Linus Torvalds <torvalds@ppc970.osdl.org> Sat Apr 9 12:02:30 2005 105 106 Make "git-fsck-cache" print out all the root commits it finds. 107 108 Once I do the reference tracking, I'll also make it print out all the 109 HEAD commits it finds, which is even more interesting. 110 111in case you care). 112 113Output format 114------------- 115include::diff-format.txt[] 116 117 118Author 119------ 120Written by Linus Torvalds <torvalds@osdl.org> 121 122Documentation 123-------------- 124Documentation by David Greaves, Junio C Hamano and the git-list <git@vger.kernel.org>. 125 126GIT 127--- 128Part of the link:git.html[git] suite 129