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|iso-strict|rfc|short) ]
49 [ [ \--objects | \--objects-edge | \--objects-edge-aggressive ]
51 [ \--pretty | \--header ]
58 [ \--no-walk ] [ \--do-walk ]
59 [ \--use-bitmap-index ]
60 <commit>... [ \-- <paths>... ]
65 List commits that are reachable by following the `parent` links from the
66 given commit(s), but exclude commits that are reachable from the one(s)
67 given with a '{caret}' in front of them. The output is given in reverse
68 chronological order by default.
70 You can think of this as a set operation. Commits given on the command
71 line form a set of commits that are reachable from any of them, and then
72 commits reachable from any of the ones given with '{caret}' in front are
73 subtracted from that set. The remaining commits are what comes out in the
74 command's output. Various other options and paths parameters can be used
75 to further limit the result.
77 Thus, the following command:
79 -----------------------------------------------------------------------
80 $ git rev-list foo bar ^baz
81 -----------------------------------------------------------------------
83 means "list all the commits which are reachable from 'foo' or 'bar', but
86 A special notation "'<commit1>'..'<commit2>'" can be used as a
87 short-hand for "{caret}'<commit1>' '<commit2>'". For example, either of
88 the following may be used interchangeably:
90 -----------------------------------------------------------------------
91 $ git rev-list origin..HEAD
92 $ git rev-list HEAD ^origin
93 -----------------------------------------------------------------------
95 Another special notation is "'<commit1>'...'<commit2>'" which is useful
96 for merges. The resulting set of commits is the symmetric difference
97 between the two operands. The following two commands are equivalent:
99 -----------------------------------------------------------------------
100 $ git rev-list A B --not $(git merge-base --all A B)
102 -----------------------------------------------------------------------
104 'rev-list' is a very essential Git command, since it
105 provides the ability to build and traverse commit ancestry graphs. For
106 this reason, it has a lot of different options that enables it to be
107 used by commands as different as 'git bisect' and
114 include::rev-list-options.txt[]
116 include::pretty-formats.txt[]
120 Part of the linkgit:git[1] suite