1git-rev-list(1) 2=============== 3 4NAME 5---- 6git-rev-list - Lists commit objects in reverse chronological order 7 8 9SYNOPSIS 10-------- 11[verse] 12'git rev-list' [ \--max-count=<number> ] 13 [ \--skip=<number> ] 14 [ \--max-age=<timestamp> ] 15 [ \--min-age=<timestamp> ] 16 [ \--sparse ] 17 [ \--merges ] 18 [ \--no-merges ] 19 [ \--min-parents=<number> ] 20 [ \--no-min-parents ] 21 [ \--max-parents=<number> ] 22 [ \--no-max-parents ] 23 [ \--first-parent ] 24 [ \--remove-empty ] 25 [ \--full-history ] 26 [ \--not ] 27 [ \--all ] 28 [ \--branches[=<pattern>] ] 29 [ \--tags[=<pattern>] ] 30 [ \--remotes[=<pattern>] ] 31 [ \--glob=<glob-pattern> ] 32 [ \--ignore-missing ] 33 [ \--stdin ] 34 [ \--quiet ] 35 [ \--topo-order ] 36 [ \--parents ] 37 [ \--timestamp ] 38 [ \--left-right ] 39 [ \--left-only ] 40 [ \--right-only ] 41 [ \--cherry-mark ] 42 [ \--cherry-pick ] 43 [ \--encoding[=<encoding>] ] 44 [ \--(author|committer|grep)=<pattern> ] 45 [ \--regexp-ignore-case | -i ] 46 [ \--extended-regexp | -E ] 47 [ \--fixed-strings | -F ] 48 [ \--date=(local|relative|default|iso|rfc|short) ] 49 [ [\--objects | \--objects-edge] [ \--unpacked ] ] 50 [ \--pretty | \--header ] 51 [ \--bisect ] 52 [ \--bisect-vars ] 53 [ \--bisect-all ] 54 [ \--merge ] 55 [ \--reverse ] 56 [ \--walk-reflogs ] 57 [ \--no-walk ] [ \--do-walk ] 58 <commit>... [ \-- <paths>... ] 59 60DESCRIPTION 61----------- 62 63List commits that are reachable by following the `parent` links from the 64given commit(s), but exclude commits that are reachable from the one(s) 65given with a '{caret}' in front of them. The output is given in reverse 66chronological order by default. 67 68You can think of this as a set operation. Commits given on the command 69line form a set of commits that are reachable from any of them, and then 70commits reachable from any of the ones given with '{caret}' in front are 71subtracted from that set. The remaining commits are what comes out in the 72command's output. Various other options and paths parameters can be used 73to further limit the result. 74 75Thus, the following command: 76 77----------------------------------------------------------------------- 78 $ git rev-list foo bar ^baz 79----------------------------------------------------------------------- 80 81means "list all the commits which are reachable from 'foo' or 'bar', but 82not from 'baz'". 83 84A special notation "'<commit1>'..'<commit2>'" can be used as a 85short-hand for "{caret}'<commit1>' '<commit2>'". For example, either of 86the following may be used interchangeably: 87 88----------------------------------------------------------------------- 89 $ git rev-list origin..HEAD 90 $ git rev-list HEAD ^origin 91----------------------------------------------------------------------- 92 93Another special notation is "'<commit1>'...'<commit2>'" which is useful 94for merges. The resulting set of commits is the symmetric difference 95between the two operands. The following two commands are equivalent: 96 97----------------------------------------------------------------------- 98 $ git rev-list A B --not $(git merge-base --all A B) 99 $ git rev-list A...B 100----------------------------------------------------------------------- 101 102'rev-list' is a very essential Git command, since it 103provides the ability to build and traverse commit ancestry graphs. For 104this reason, it has a lot of different options that enables it to be 105used by commands as different as 'git bisect' and 106'git repack'. 107 108OPTIONS 109------- 110 111:git-rev-list: 1 112include::rev-list-options.txt[] 113 114include::pretty-formats.txt[] 115 116GIT 117--- 118Part of the linkgit:git[1] suite