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> ]
19 [ \--min-parents=<number> ]
21 [ \--max-parents=<number> ]
28 [ \--branches[=<pattern>] ]
29 [ \--tags[=<pattern>] ]
30 [ \--remotes[=<pattern>] ]
31 [ \--glob=<glob-pattern> ]
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 ]
57 [ \--no-walk ] [ \--do-walk ]
58 [ \--use-bitmap-index ]
59 <commit>... [ \-- <paths>... ]
64 List commits that are reachable by following the `parent` links from the
65 given commit(s), but exclude commits that are reachable from the one(s)
66 given with a '{caret}' in front of them. The output is given in reverse
67 chronological order by default.
69 You can think of this as a set operation. Commits given on the command
70 line form a set of commits that are reachable from any of them, and then
71 commits reachable from any of the ones given with '{caret}' in front are
72 subtracted from that set. The remaining commits are what comes out in the
73 command's output. Various other options and paths parameters can be used
74 to further limit the result.
76 Thus, the following command:
78 -----------------------------------------------------------------------
79 $ git rev-list foo bar ^baz
80 -----------------------------------------------------------------------
82 means "list all the commits which are reachable from 'foo' or 'bar', but
85 A special notation "'<commit1>'..'<commit2>'" can be used as a
86 short-hand for "{caret}'<commit1>' '<commit2>'". For example, either of
87 the following may be used interchangeably:
89 -----------------------------------------------------------------------
90 $ git rev-list origin..HEAD
91 $ git rev-list HEAD ^origin
92 -----------------------------------------------------------------------
94 Another special notation is "'<commit1>'...'<commit2>'" which is useful
95 for merges. The resulting set of commits is the symmetric difference
96 between the two operands. The following two commands are equivalent:
98 -----------------------------------------------------------------------
99 $ git rev-list A B --not $(git merge-base --all A B)
101 -----------------------------------------------------------------------
103 'rev-list' is a very essential Git command, since it
104 provides the ability to build and traverse commit ancestry graphs. For
105 this reason, it has a lot of different options that enables it to be
106 used by commands as different as 'git bisect' and
113 include::rev-list-options.txt[]
115 include::pretty-formats.txt[]
119 Part of the linkgit:git[1] suite