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> ]
24 [ \--branches[=<pattern>] ]
25 [ \--tags[=<pattern>] ]
26 [ \--remotes[=<pattern>] ]
27 [ \--glob=<glob-pattern> ]
38 [ \--encoding[=<encoding>] ]
39 [ \--(author|committer|grep)=<pattern> ]
40 [ \--regexp-ignore-case | -i ]
41 [ \--extended-regexp | -E ]
42 [ \--fixed-strings | -F ]
43 [ \--date=(local|relative|default|iso|rfc|short) ]
44 [ [\--objects | \--objects-edge] [ \--unpacked ] ]
45 [ \--pretty | \--header ]
52 [ \--no-walk ] [ \--do-walk ]
53 <commit>... [ \-- <paths>... ]
58 List commits that are reachable by following the `parent` links from the
59 given commit(s), but exclude commits that are reachable from the one(s)
60 given with a '{caret}' in front of them. The output is given in reverse
61 chronological order by default.
63 You can think of this as a set operation. Commits given on the command
64 line form a set of commits that are reachable from any of them, and then
65 commits reachable from any of the ones given with '{caret}' in front are
66 subtracted from that set. The remaining commits are what comes out in the
67 command's output. Various other options and paths parameters can be used
68 to further limit the result.
70 Thus, the following command:
72 -----------------------------------------------------------------------
73 $ git rev-list foo bar ^baz
74 -----------------------------------------------------------------------
76 means "list all the commits which are reachable from 'foo' or 'bar', but
79 A special notation "'<commit1>'..'<commit2>'" can be used as a
80 short-hand for "{caret}'<commit1>' '<commit2>'". For example, either of
81 the following may be used interchangeably:
83 -----------------------------------------------------------------------
84 $ git rev-list origin..HEAD
85 $ git rev-list HEAD ^origin
86 -----------------------------------------------------------------------
88 Another special notation is "'<commit1>'...'<commit2>'" which is useful
89 for merges. The resulting set of commits is the symmetric difference
90 between the two operands. The following two commands are equivalent:
92 -----------------------------------------------------------------------
93 $ git rev-list A B --not $(git merge-base --all A B)
95 -----------------------------------------------------------------------
97 'rev-list' is a very essential git command, since it
98 provides the ability to build and traverse commit ancestry graphs. For
99 this reason, it has a lot of different options that enables it to be
100 used by commands as different as 'git bisect' and
107 include::rev-list-options.txt[]
109 include::pretty-formats.txt[]
113 Part of the linkgit:git[1] suite