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