2005-05-10 23:32:30 +02:00
|
|
|
git-rev-list(1)
|
|
|
|
===============
|
|
|
|
|
|
|
|
NAME
|
|
|
|
----
|
|
|
|
git-rev-list - Lists commit objects in reverse chronological order
|
|
|
|
|
|
|
|
|
|
|
|
SYNOPSIS
|
|
|
|
--------
|
2005-12-31 18:37:15 +01:00
|
|
|
[verse]
|
2019-10-05 02:13:08 +02:00
|
|
|
'git rev-list' [<options>] <commit>... [[--] <path>...]
|
2005-05-10 23:32:30 +02:00
|
|
|
|
|
|
|
DESCRIPTION
|
|
|
|
-----------
|
2006-09-01 00:37:15 +02:00
|
|
|
|
2009-08-05 18:42:33 +02:00
|
|
|
List commits that are reachable by following the `parent` links from the
|
|
|
|
given commit(s), but exclude commits that are reachable from the one(s)
|
|
|
|
given with a '{caret}' in front of them. The output is given in reverse
|
|
|
|
chronological order by default.
|
2005-05-10 23:32:30 +02:00
|
|
|
|
2009-08-05 18:42:33 +02:00
|
|
|
You can think of this as a set operation. Commits given on the command
|
|
|
|
line form a set of commits that are reachable from any of them, and then
|
|
|
|
commits reachable from any of the ones given with '{caret}' in front are
|
|
|
|
subtracted from that set. The remaining commits are what comes out in the
|
|
|
|
command's output. Various other options and paths parameters can be used
|
|
|
|
to further limit the result.
|
|
|
|
|
|
|
|
Thus, the following command:
|
2006-09-01 00:37:15 +02:00
|
|
|
|
|
|
|
-----------------------------------------------------------------------
|
2008-06-30 08:09:04 +02:00
|
|
|
$ git rev-list foo bar ^baz
|
2006-09-01 00:37:15 +02:00
|
|
|
-----------------------------------------------------------------------
|
|
|
|
|
2009-08-05 18:42:33 +02:00
|
|
|
means "list all the commits which are reachable from 'foo' or 'bar', but
|
|
|
|
not from 'baz'".
|
2005-07-29 20:10:46 +02:00
|
|
|
|
2006-09-01 00:37:15 +02:00
|
|
|
A special notation "'<commit1>'..'<commit2>'" can be used as a
|
|
|
|
short-hand for "{caret}'<commit1>' '<commit2>'". For example, either of
|
|
|
|
the following may be used interchangeably:
|
2005-10-30 10:03:45 +01:00
|
|
|
|
2006-09-01 00:37:15 +02:00
|
|
|
-----------------------------------------------------------------------
|
2008-06-30 08:09:04 +02:00
|
|
|
$ git rev-list origin..HEAD
|
|
|
|
$ git rev-list HEAD ^origin
|
2006-09-01 00:37:15 +02:00
|
|
|
-----------------------------------------------------------------------
|
|
|
|
|
|
|
|
Another special notation is "'<commit1>'...'<commit2>'" which is useful
|
|
|
|
for merges. The resulting set of commits is the symmetric difference
|
2006-07-02 01:29:37 +02:00
|
|
|
between the two operands. The following two commands are equivalent:
|
|
|
|
|
2006-09-01 00:37:15 +02:00
|
|
|
-----------------------------------------------------------------------
|
2008-06-30 08:09:04 +02:00
|
|
|
$ git rev-list A B --not $(git merge-base --all A B)
|
|
|
|
$ git rev-list A...B
|
2006-09-01 00:37:15 +02:00
|
|
|
-----------------------------------------------------------------------
|
|
|
|
|
2013-01-21 20:17:53 +01:00
|
|
|
'rev-list' is a very essential Git command, since it
|
2006-09-01 00:37:15 +02:00
|
|
|
provides the ability to build and traverse commit ancestry graphs. For
|
|
|
|
this reason, it has a lot of different options that enables it to be
|
2010-01-10 00:33:00 +01:00
|
|
|
used by commands as different as 'git bisect' and
|
|
|
|
'git repack'.
|
2005-10-30 10:03:45 +01:00
|
|
|
|
2005-10-03 19:16:30 +02:00
|
|
|
OPTIONS
|
|
|
|
-------
|
2006-09-01 00:37:15 +02:00
|
|
|
|
2008-01-18 23:58:57 +01:00
|
|
|
:git-rev-list: 1
|
|
|
|
include::rev-list-options.txt[]
|
2007-05-14 01:25:45 +02:00
|
|
|
|
|
|
|
include::pretty-formats.txt[]
|
|
|
|
|
2005-05-10 23:32:30 +02:00
|
|
|
GIT
|
|
|
|
---
|
2008-06-06 09:07:32 +02:00
|
|
|
Part of the linkgit:git[1] suite
|