6 git-rev-list - Lists commit objects in reverse chronological order
12 'git-rev-list' [ \--max-count=number ]
13 [ \--max-age=timestamp ]
14 [ \--min-age=timestamp ]
22 [ [\--objects | \--objects-edge] [ \--unpacked ] ]
23 [ \--pretty | \--header ]
26 <commit>... [ \-- <paths>... ]
31 Lists commit objects in reverse chronological order starting at the
32 given commit(s), taking ancestry relationship into account. This is
33 useful to produce human-readable log output.
35 Commits which are stated with a preceding '{caret}' cause listing to
36 stop at that point. Their parents are implied. Thus the following
39 -----------------------------------------------------------------------
40 $ git-rev-list foo bar ^baz
41 -----------------------------------------------------------------------
43 means "list all the commits which are included in 'foo' and 'bar', but
46 A special notation "'<commit1>'..'<commit2>'" can be used as a
47 short-hand for "{caret}'<commit1>' '<commit2>'". For example, either of
48 the following may be used interchangeably:
50 -----------------------------------------------------------------------
51 $ git-rev-list origin..HEAD
52 $ git-rev-list HEAD ^origin
53 -----------------------------------------------------------------------
55 Another special notation is "'<commit1>'...'<commit2>'" which is useful
56 for merges. The resulting set of commits is the symmetric difference
57 between the two operands. The following two commands are equivalent:
59 -----------------------------------------------------------------------
60 $ git-rev-list A B --not $(git-merge-base --all A B)
62 -----------------------------------------------------------------------
64 gitlink:git-rev-list[1] is a very essential git program, since it
65 provides the ability to build and traverse commit ancestry graphs. For
66 this reason, it has a lot of different options that enables it to be
67 used by commands as different as gitlink:git-bisect[1] and
68 gitlink:git-repack[1].
76 Using these options, gitlink:git-rev-list[1] will act similar to the
77 more specialized family of commit log tools: gitlink:git-log[1],
78 gitlink:git-show[1], and gitlink:git-whatchanged[1]
80 --pretty[='<format>']::
82 Pretty print the contents of the commit logs in a given format,
83 where '<format>' can be one of 'raw', 'medium', 'short', 'full',
84 and 'oneline'. When left out the format default to 'medium'.
88 Show dates relative to the current time, e.g. "2 hours ago".
89 Only takes effect for dates shown in human-readable format, such
90 as when using "--pretty".
94 Print the contents of the commit in raw-format; each record is
95 separated with a NUL character.
99 Print the parents of the commit.
104 Below are listed options that control the formatting of diff output.
105 Some of them are specific to gitlink:git-rev-list[1], however other diff
106 options may be given. See gitlink:git-diff-files[1] for more options.
110 This flag changes the way a merge commit is displayed. It shows
111 the differences from each of the parents to the merge result
112 simultaneously instead of showing pairwise diff between a parent
113 and the result one at a time. Furthermore, it lists only files
114 which were modified from all parents.
118 This flag implies the '-c' options and further compresses the
119 patch output by omitting hunks that show differences from only
120 one parent, or show the same change from all but one parent for
125 Show recursive diffs.
129 Show the tree objects in the diff output. This implies '-r'.
134 Besides specifying a range of commits that should be listed using the
135 special notations explained in the description, additional commit
136 limiting may be applied.
140 -n 'number', --max-count='number'::
142 Limit the number of commits output.
144 --since='date', --after='date'::
146 Show commits more recent than a specific date.
148 --until='date', --before='date'::
150 Show commits older than a specific date.
152 --max-age='timestamp', --min-age='timestamp'::
154 Limit the commits output to specified time range.
158 Stop when a given path disappears from the tree.
162 Do not print commits with more than one parent.
166 Reverses the meaning of the '{caret}' prefix (or lack thereof)
167 for all following revision specifiers, up to the next '--not'.
171 Pretend as if all the refs in `$GIT_DIR/refs/` are listed on the
172 command line as '<commit>'.
176 After a failed merge, show refs that touch files having a
177 conflict and don't exist on all heads to merge.
181 Output uninteresting commits at the boundary, which are usually
186 When optional paths are given, the default behaviour ('--dense') is to
187 only output commits that changes at least one of them, and also ignore
188 merges that do not touch the given paths.
190 Use the '--sparse' flag to makes the command output all eligible commits
191 (still subject to count and age limitation), but apply merge
192 simplification nevertheless.
196 Limit output to the one commit object which is roughly halfway between
197 the included and excluded commits. Thus, if
199 -----------------------------------------------------------------------
200 $ git-rev-list --bisect foo ^bar ^baz
201 -----------------------------------------------------------------------
203 outputs 'midpoint', the output of the two commands
205 -----------------------------------------------------------------------
206 $ git-rev-list foo ^midpoint
207 $ git-rev-list midpoint ^bar ^baz
208 -----------------------------------------------------------------------
210 would be of roughly the same length. Finding the change which
211 introduces a regression is thus reduced to a binary search: repeatedly
212 generate and test new 'midpoint's until the commit chain is of length
220 By default, the commits are shown in reverse chronological order.
224 This option makes them appear in topological order (i.e.
225 descendant commits are shown before their parents).
229 This option is similar to '--topo-order' in the sense that no
230 parent comes before all of its children, but otherwise things
231 are still ordered in the commit timestamp order.
236 These options are mostly targeted for packing of git repositories.
240 Print the object IDs of any object referenced by the listed
241 commits. 'git-rev-list --objects foo ^bar' thus means "send me
242 all object IDs which I need to download if I have the commit
243 object 'bar', but not 'foo'".
247 Similar to '--objects', but also print the IDs of excluded
248 commits prefixed with a "-" character. This is used by
249 gitlink:git-pack-objects[1] to build "thin" pack, which records
250 objects in deltified form based on objects contained in these
251 excluded commits to reduce network traffic.
255 Only useful with '--objects'; print the object IDs that are not
260 Written by Linus Torvalds <torvalds@osdl.org>
264 Documentation by David Greaves, Junio C Hamano, Jonas Fonseca
265 and the git-list <git@vger.kernel.org>.
269 Part of the gitlink:git[7] suite