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] [-R] [-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 Output diff in reverse. 41 42-r:: 43 recurse 44 45-z:: 46 \0 line termination on output 47 48--stdin:: 49 When '--stdin' is specified, the command does not take 50 <tree-ish> arguments from the command line. Instead, it 51 reads either one <commit> or a pair of <tree-ish> 52 separated with a single space from its standard input. 53+ 54When a single commit is given on one line of such input, it compares 55the commit with its parents. The following flags further affects its 56behaviour. This does not apply to the case where two <tree-ish> 57separated with a single space are given. 58 59-m:: 60 By default, "git-diff-tree --stdin" does not show 61 differences for merge commits. With this flag, it shows 62 differences to that commit from all of its parents. 63 64-s:: 65 By default, "git-diff-tree --stdin" shows differences, 66 either in machine-readable form (without '-p') or in patch 67 form (with '-p'). This output can be supressed. It is 68 only useful with '-v' flag. 69 70-v:: 71 This flag causes "git-diff-tree --stdin" to also show 72 the commit message before the differences. 73 74 75Limiting Output 76--------------- 77If you're only interested in differences in a subset of files, for 78example some architecture-specific files, you might do: 79 80 git-diff-tree -r <tree-ish> <tree-ish> arch/ia64 include/asm-ia64 81 82and it will only show you what changed in those two directories. 83 84Or if you are searching for what changed in just `kernel/sched.c`, just do 85 86 git-diff-tree -r <tree-ish> <tree-ish> kernel/sched.c 87 88and it will ignore all differences to other files. 89 90The pattern is always the prefix, and is matched exactly. There are no 91wildcards. Even stricter, it has to match complete path comonent. 92I.e. "foo" does not pick up `foobar.h`. "foo" does match `foo/bar.h` 93so it can be used to name subdirectories. 94 95An example of normal usage is: 96 97 torvalds@ppc970:~/git> git-diff-tree 5319e4...... 98 *100664->100664 blob ac348b.......->a01513....... git-fsck-cache.c 99 100which tells you that the last commit changed just one file (it's from 101this one: 102 103 commit 3c6f7ca19ad4043e9e72fa94106f352897e651a8 104 tree 5319e4d609cdd282069cc4dce33c1db559539b03 105 parent b4e628ea30d5ab3606119d2ea5caeab141d38df7 106 author Linus Torvalds <torvalds@ppc970.osdl.org> Sat Apr 9 12:02:30 2005 107 committer Linus Torvalds <torvalds@ppc970.osdl.org> Sat Apr 9 12:02:30 2005 108 109 Make "git-fsck-cache" print out all the root commits it finds. 110 111 Once I do the reference tracking, I'll also make it print out all the 112 HEAD commits it finds, which is even more interesting. 113 114in case you care). 115 116Output format 117------------- 118include::diff-format.txt[] 119 120 121Author 122------ 123Written by Linus Torvalds <torvalds@osdl.org> 124 125Documentation 126-------------- 127Documentation by David Greaves, Junio C Hamano and the git-list <git@vger.kernel.org>. 128 129GIT 130--- 131Part of the link:git.html[git] suite 132