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