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 [ \--no-merges ] 18 [ \--first-parent ] 19 [ \--remove-empty ] 20 [ \--full-history ] 21 [ \--not ] 22 [ \--all ] 23 [ \--stdin ] 24 [ \--quiet ] 25 [ \--topo-order ] 26 [ \--parents ] 27 [ \--timestamp ] 28 [ \--left-right ] 29 [ \--cherry-pick ] 30 [ \--encoding[=<encoding>] ] 31 [ \--(author|committer|grep)=<pattern> ] 32 [ \--regexp-ignore-case | \-i ] 33 [ \--extended-regexp | \-E ] 34 [ \--date={local|relative|default|iso|rfc|short} ] 35 [ [\--objects | \--objects-edge] [ \--unpacked ] ] 36 [ \--pretty | \--header ] 37 [ \--bisect ] 38 [ \--bisect-vars ] 39 [ \--bisect-all ] 40 [ \--merge ] 41 [ \--reverse ] 42 [ \--walk-reflogs ] 43 [ \--no-walk ] [ \--do-walk ] 44 <commit>... [ \-- <paths>... ] 45 46DESCRIPTION 47----------- 48 49Lists commit objects in reverse chronological order starting at the 50given commit(s), taking ancestry relationship into account. This is 51useful to produce human-readable log output. 52 53Commits which are stated with a preceding '{caret}' cause listing to 54stop at that point. Their parents are implied. Thus the following 55command: 56 57----------------------------------------------------------------------- 58 $ git-rev-list foo bar ^baz 59----------------------------------------------------------------------- 60 61means "list all the commits which are included in 'foo' and 'bar', but 62not in 'baz'". 63 64A special notation "'<commit1>'..'<commit2>'" can be used as a 65short-hand for "{caret}'<commit1>' '<commit2>'". For example, either of 66the following may be used interchangeably: 67 68----------------------------------------------------------------------- 69 $ git-rev-list origin..HEAD 70 $ git-rev-list HEAD ^origin 71----------------------------------------------------------------------- 72 73Another special notation is "'<commit1>'...'<commit2>'" which is useful 74for merges. The resulting set of commits is the symmetric difference 75between the two operands. The following two commands are equivalent: 76 77----------------------------------------------------------------------- 78 $ git-rev-list A B --not $(git-merge-base --all A B) 79 $ git-rev-list A...B 80----------------------------------------------------------------------- 81 82linkgit:git-rev-list[1] is a very essential git program, since it 83provides the ability to build and traverse commit ancestry graphs. For 84this reason, it has a lot of different options that enables it to be 85used by commands as different as linkgit:git-bisect[1] and 86linkgit:git-repack[1]. 87 88OPTIONS 89------- 90 91:git-rev-list: 1 92include::rev-list-options.txt[] 93 94include::pretty-formats.txt[] 95 96 97Author 98------ 99Written by Linus Torvalds <torvalds@osdl.org> 100 101Documentation 102-------------- 103Documentation by David Greaves, Junio C Hamano, Jonas Fonseca 104and the git-list <git@vger.kernel.org>. 105 106GIT 107--- 108Part of the linkgit:git[7] suite