6 git-rev-list - Lists commit objects in reverse chronological order
12 'git-rev-list' [ \--max-count=number ]
14 [ \--max-age=timestamp ]
15 [ \--min-age=timestamp ]
30 [ \--encoding[=<encoding>] ]
31 [ \--(author|committer|grep)=<pattern> ]
32 [ \--regexp-ignore-case | \-i ]
33 [ \--extended-regexp | \-E ]
34 [ \--fixed-strings | \-F ]
35 [ \--date={local|relative|default|iso|rfc|short} ]
36 [ [\--objects | \--objects-edge] [ \--unpacked ] ]
37 [ \--pretty | \--header ]
44 [ \--no-walk ] [ \--do-walk ]
45 <commit>... [ \-- <paths>... ]
50 Lists commit objects in reverse chronological order starting at the
51 given commit(s), taking ancestry relationship into account. This is
52 useful to produce human-readable log output.
54 Commits which are stated with a preceding '{caret}' cause listing to
55 stop at that point. Their parents are implied. Thus the following
58 -----------------------------------------------------------------------
59 $ git-rev-list foo bar ^baz
60 -----------------------------------------------------------------------
62 means "list all the commits which are included in 'foo' and 'bar', but
65 A special notation "'<commit1>'..'<commit2>'" can be used as a
66 short-hand for "{caret}'<commit1>' '<commit2>'". For example, either of
67 the following may be used interchangeably:
69 -----------------------------------------------------------------------
70 $ git-rev-list origin..HEAD
71 $ git-rev-list HEAD ^origin
72 -----------------------------------------------------------------------
74 Another special notation is "'<commit1>'...'<commit2>'" which is useful
75 for merges. The resulting set of commits is the symmetric difference
76 between the two operands. The following two commands are equivalent:
78 -----------------------------------------------------------------------
79 $ git-rev-list A B --not $(git-merge-base --all A B)
81 -----------------------------------------------------------------------
83 linkgit:git-rev-list[1] is a very essential git program, since it
84 provides the ability to build and traverse commit ancestry graphs. For
85 this reason, it has a lot of different options that enables it to be
86 used by commands as different as linkgit:git-bisect[1] and
87 linkgit:git-repack[1].
93 include::rev-list-options.txt[]
95 include::pretty-formats.txt[]
100 Written by Linus Torvalds <torvalds@osdl.org>
104 Documentation by David Greaves, Junio C Hamano, Jonas Fonseca
105 and the git-list <git@vger.kernel.org>.
109 Part of the linkgit:git[7] suite