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 ]
28 [ \--encoding[=<encoding>] ]
29 [ \--(author|committer|grep)=<pattern> ]
30 [ \--regexp-ignore-case | \-i ]
31 [ \--extended-regexp | \-E ]
32 [ \--date={local|relative|default|iso|rfc|short} ]
33 [ [\--objects | \--objects-edge] [ \--unpacked ] ]
34 [ \--pretty | \--header ]
40 <commit>... [ \-- <paths>... ]
45 Lists commit objects in reverse chronological order starting at the
46 given commit(s), taking ancestry relationship into account. This is
47 useful to produce human-readable log output.
49 Commits which are stated with a preceding '{caret}' cause listing to
50 stop at that point. Their parents are implied. Thus the following
53 -----------------------------------------------------------------------
54 $ git-rev-list foo bar ^baz
55 -----------------------------------------------------------------------
57 means "list all the commits which are included in 'foo' and 'bar', but
60 A special notation "'<commit1>'..'<commit2>'" can be used as a
61 short-hand for "{caret}'<commit1>' '<commit2>'". For example, either of
62 the following may be used interchangeably:
64 -----------------------------------------------------------------------
65 $ git-rev-list origin..HEAD
66 $ git-rev-list HEAD ^origin
67 -----------------------------------------------------------------------
69 Another special notation is "'<commit1>'...'<commit2>'" which is useful
70 for merges. The resulting set of commits is the symmetric difference
71 between the two operands. The following two commands are equivalent:
73 -----------------------------------------------------------------------
74 $ git-rev-list A B --not $(git-merge-base --all A B)
76 -----------------------------------------------------------------------
78 gitlink:git-rev-list[1] is a very essential git program, since it
79 provides the ability to build and traverse commit ancestry graphs. For
80 this reason, it has a lot of different options that enables it to be
81 used by commands as different as gitlink:git-bisect[1] and
82 gitlink:git-repack[1].
90 Using these options, gitlink:git-rev-list[1] will act similar to the
91 more specialized family of commit log tools: gitlink:git-log[1],
92 gitlink:git-show[1], and gitlink:git-whatchanged[1]
94 include::pretty-options.txt[]
98 Synonym for `--date=relative`.
100 --date={relative,local,default,iso,rfc}::
102 Only takes effect for dates shown in human-readable format, such
103 as when using "--pretty".
105 `--date=relative` shows dates relative to the current time,
108 `--date=local` shows timestamps in user's local timezone.
110 `--date=iso` (or `--date=iso8601`) shows timestamps in ISO 8601 format.
112 `--date=rfc` (or `--date=rfc2822`) shows timestamps in RFC 2822
113 format, often found in E-mail messages.
115 `--date=short` shows only date but not time, in `YYYY-MM-DD` fomat.
117 `--date=default` shows timestamps in the original timezone
118 (either committer's or author's).
122 Print the contents of the commit in raw-format; each record is
123 separated with a NUL character.
127 Print the parents of the commit.
130 Print the raw commit timestamp.
134 Mark which side of a symmetric diff a commit is reachable from.
135 Commits from the left side are prefixed with `<` and those from
136 the right with `>`. If combined with `--boundary`, those
137 commits are prefixed with `-`.
139 For example, if you have this topology:
141 -----------------------------------------------------------------------
146 o---x---a---a branch A
147 -----------------------------------------------------------------------
149 you would get an output line this:
151 -----------------------------------------------------------------------
152 $ git rev-list --left-right --boundary --pretty=oneline A...B
160 -----------------------------------------------------------------------
165 Below are listed options that control the formatting of diff output.
166 Some of them are specific to gitlink:git-rev-list[1], however other diff
167 options may be given. See gitlink:git-diff-files[1] for more options.
171 This flag changes the way a merge commit is displayed. It shows
172 the differences from each of the parents to the merge result
173 simultaneously instead of showing pairwise diff between a parent
174 and the result one at a time. Furthermore, it lists only files
175 which were modified from all parents.
179 This flag implies the '-c' options and further compresses the
180 patch output by omitting hunks that show differences from only
181 one parent, or show the same change from all but one parent for
186 Show recursive diffs.
190 Show the tree objects in the diff output. This implies '-r'.
195 Besides specifying a range of commits that should be listed using the
196 special notations explained in the description, additional commit
197 limiting may be applied.
201 -n 'number', --max-count='number'::
203 Limit the number of commits output.
207 Skip 'number' commits before starting to show the commit output.
209 --since='date', --after='date'::
211 Show commits more recent than a specific date.
213 --until='date', --before='date'::
215 Show commits older than a specific date.
217 --max-age='timestamp', --min-age='timestamp'::
219 Limit the commits output to specified time range.
221 --author='pattern', --committer='pattern'::
223 Limit the commits output to ones with author/committer
224 header lines that match the specified pattern (regular expression).
228 Limit the commits output to ones with log message that
229 matches the specified pattern (regular expression).
231 -i, --regexp-ignore-case::
233 Match the regexp limiting patterns without regard to letters case.
235 -E, --extended-regexp::
237 Consider the limiting patterns to be extended regular expressions
238 instead of the default basic regular expressions.
242 Stop when a given path disappears from the tree.
246 Show also parts of history irrelevant to current state of a given
247 path. This turns off history simplification, which removed merges
248 which didn't change anything at all at some child. It will still actually
249 simplify away merges that didn't change anything at all into either
254 Do not print commits with more than one parent.
258 Reverses the meaning of the '{caret}' prefix (or lack thereof)
259 for all following revision specifiers, up to the next '--not'.
263 Pretend as if all the refs in `$GIT_DIR/refs/` are listed on the
264 command line as '<commit>'.
268 In addition to the '<commit>' listed on the command
269 line, read them from the standard input.
273 Omit any commit that introduces the same change as
274 another commit on the "other side" when the set of
275 commits are limited with symmetric difference.
277 For example, if you have two branches, `A` and `B`, a usual way
278 to list all commits on only one side of them is with
279 `--left-right`, like the example above in the description of
280 that option. It however shows the commits that were cherry-picked
281 from the other branch (for example, "3rd on b" may be cherry-picked
282 from branch A). With this option, such pairs of commits are
283 excluded from the output.
287 Instead of walking the commit ancestry chain, walk
288 reflog entries from the most recent one to older ones.
289 When this option is used you cannot specify commits to
290 exclude (that is, '{caret}commit', 'commit1..commit2',
291 nor 'commit1...commit2' notations cannot be used).
293 With '\--pretty' format other than oneline (for obvious reasons),
294 this causes the output to have two extra lines of information
295 taken from the reflog. By default, 'commit@\{Nth}' notation is
296 used in the output. When the starting commit is specified as
297 'commit@{now}', output also uses 'commit@\{timestamp}' notation
298 instead. Under '\--pretty=oneline', the commit message is
299 prefixed with this information on the same line.
303 After a failed merge, show refs that touch files having a
304 conflict and don't exist on all heads to merge.
308 Output uninteresting commits at the boundary, which are usually
313 When optional paths are given, the default behaviour ('--dense') is to
314 only output commits that changes at least one of them, and also ignore
315 merges that do not touch the given paths.
317 Use the '--sparse' flag to makes the command output all eligible commits
318 (still subject to count and age limitation), but apply merge
319 simplification nevertheless.
323 Limit output to the one commit object which is roughly halfway between
324 the included and excluded commits. Thus, if
326 -----------------------------------------------------------------------
327 $ git-rev-list --bisect foo ^bar ^baz
328 -----------------------------------------------------------------------
330 outputs 'midpoint', the output of the two commands
332 -----------------------------------------------------------------------
333 $ git-rev-list foo ^midpoint
334 $ git-rev-list midpoint ^bar ^baz
335 -----------------------------------------------------------------------
337 would be of roughly the same length. Finding the change which
338 introduces a regression is thus reduced to a binary search: repeatedly
339 generate and test new 'midpoint's until the commit chain is of length
344 This calculates the same as `--bisect`, but outputs text ready
345 to be eval'ed by the shell. These lines will assign the name of
346 the midpoint revision to the variable `bisect_rev`, and the
347 expected number of commits to be tested after `bisect_rev` is
348 tested to `bisect_nr`, the expected number of commits to be
349 tested if `bisect_rev` turns out to be good to `bisect_good`,
350 the expected number of commits to be tested if `bisect_rev`
351 turns out to be bad to `bisect_bad`, and the number of commits
352 we are bisecting right now to `bisect_all`.
359 By default, the commits are shown in reverse chronological order.
363 This option makes them appear in topological order (i.e.
364 descendant commits are shown before their parents).
368 This option is similar to '--topo-order' in the sense that no
369 parent comes before all of its children, but otherwise things
370 are still ordered in the commit timestamp order.
374 Output the commits in reverse order.
379 These options are mostly targeted for packing of git repositories.
383 Print the object IDs of any object referenced by the listed
384 commits. 'git-rev-list --objects foo ^bar' thus means "send me
385 all object IDs which I need to download if I have the commit
386 object 'bar', but not 'foo'".
390 Similar to '--objects', but also print the IDs of excluded
391 commits prefixed with a "-" character. This is used by
392 gitlink:git-pack-objects[1] to build "thin" pack, which records
393 objects in deltified form based on objects contained in these
394 excluded commits to reduce network traffic.
398 Only useful with '--objects'; print the object IDs that are not
402 include::pretty-formats.txt[]
407 Written by Linus Torvalds <torvalds@osdl.org>
411 Documentation by David Greaves, Junio C Hamano, Jonas Fonseca
412 and the git-list <git@vger.kernel.org>.
416 Part of the gitlink:git[7] suite