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|iso-strict|rfc|short) ] 49 [ [ \--objects | \--objects-edge | \--objects-edge-aggressive ] 50 [ \--unpacked ] ] 51 [ \--pretty | \--header ] 52 [ \--bisect ] 53 [ \--bisect-vars ] 54 [ \--bisect-all ] 55 [ \--merge ] 56 [ \--reverse ] 57 [ \--walk-reflogs ] 58 [ \--no-walk ] [ \--do-walk ] 59 [ \--use-bitmap-index ] 60 <commit>... [ \-- <paths>... ] 61 62DESCRIPTION 63----------- 64 65List commits that are reachable by following the `parent` links from the 66given commit(s), but exclude commits that are reachable from the one(s) 67given with a '{caret}' in front of them. The output is given in reverse 68chronological order by default. 69 70You can think of this as a set operation. Commits given on the command 71line form a set of commits that are reachable from any of them, and then 72commits reachable from any of the ones given with '{caret}' in front are 73subtracted from that set. The remaining commits are what comes out in the 74command's output. Various other options and paths parameters can be used 75to further limit the result. 76 77Thus, the following command: 78 79----------------------------------------------------------------------- 80 $ git rev-list foo bar ^baz 81----------------------------------------------------------------------- 82 83means "list all the commits which are reachable from 'foo' or 'bar', but 84not from 'baz'". 85 86A special notation "'<commit1>'..'<commit2>'" can be used as a 87short-hand for "{caret}'<commit1>' '<commit2>'". For example, either of 88the following may be used interchangeably: 89 90----------------------------------------------------------------------- 91 $ git rev-list origin..HEAD 92 $ git rev-list HEAD ^origin 93----------------------------------------------------------------------- 94 95Another special notation is "'<commit1>'...'<commit2>'" which is useful 96for merges. The resulting set of commits is the symmetric difference 97between the two operands. The following two commands are equivalent: 98 99----------------------------------------------------------------------- 100 $ git rev-list A B --not $(git merge-base --all A B) 101 $ git rev-list A...B 102----------------------------------------------------------------------- 103 104'rev-list' is a very essential Git command, since it 105provides the ability to build and traverse commit ancestry graphs. For 106this reason, it has a lot of different options that enables it to be 107used by commands as different as 'git bisect' and 108'git repack'. 109 110OPTIONS 111------- 112 113:git-rev-list: 1 114include::rev-list-options.txt[] 115 116include::pretty-formats.txt[] 117 118GIT 119--- 120Part of the linkgit:git[1] suite