Andrew's git - gitweb.git/blob - Documentation/git-rev-list.txt

   1git-rev-list(1)
   2===============
   3
   4NAME
   5----
   6git-rev-list - Lists commit objects in reverse chronological order
   7
   8
   9SYNOPSIS
  10--------
  11[verse]
  12'git-rev-list' [ \--max-count=number ]
  13             [ \--skip=number ]
  14             [ \--max-age=timestamp ]
  15             [ \--min-age=timestamp ]
  16             [ \--sparse ]
  17             [ \--no-merges ]
  18             [ \--first-parent ]
  19             [ \--remove-empty ]
  20             [ \--full-history ]
  21             [ \--not ]
  22             [ \--all ]
  23             [ \--branches ]
  24             [ \--tags ]
  25             [ \--remotes ]
  26             [ \--stdin ]
  27             [ \--quiet ]
  28             [ \--topo-order ]
  29             [ \--parents ]
  30             [ \--timestamp ]
  31             [ \--left-right ]
  32             [ \--cherry-pick ]
  33             [ \--encoding[=<encoding>] ]
  34             [ \--(author|committer|grep)=<pattern> ]
  35             [ \--regexp-ignore-case | \-i ]
  36             [ \--extended-regexp | \-E ]
  37             [ \--fixed-strings | \-F ]
  38             [ \--date={local|relative|default|iso|rfc|short} ]
  39             [ [\--objects | \--objects-edge] [ \--unpacked ] ]
  40             [ \--pretty | \--header ]
  41             [ \--bisect ]
  42             [ \--bisect-vars ]
  43             [ \--bisect-all ]
  44             [ \--merge ]
  45             [ \--reverse ]
  46             [ \--walk-reflogs ]
  47             [ \--no-walk ] [ \--do-walk ]
  48             <commit>... [ \-- <paths>... ]
  49
  50DESCRIPTION
  51-----------
  52
  53Lists commit objects in reverse chronological order starting at the
  54given commit(s), taking ancestry relationship into account.  This is
  55useful to produce human-readable log output.
  56
  57Commits which are stated with a preceding '{caret}' cause listing to
  58stop at that point. Their parents are implied. Thus the following
  59command:
  60
  61-----------------------------------------------------------------------
  62        $ git rev-list foo bar ^baz
  63-----------------------------------------------------------------------
  64
  65means "list all the commits which are included in 'foo' and 'bar', but
  66not in 'baz'".
  67
  68A special notation "'<commit1>'..'<commit2>'" can be used as a
  69short-hand for "{caret}'<commit1>' '<commit2>'". For example, either of
  70the following may be used interchangeably:
  71
  72-----------------------------------------------------------------------
  73        $ git rev-list origin..HEAD
  74        $ git rev-list HEAD ^origin
  75-----------------------------------------------------------------------
  76
  77Another special notation is "'<commit1>'...'<commit2>'" which is useful
  78for merges.  The resulting set of commits is the symmetric difference
  79between the two operands.  The following two commands are equivalent:
  80
  81-----------------------------------------------------------------------
  82        $ git rev-list A B --not $(git merge-base --all A B)
  83        $ git rev-list A...B
  84-----------------------------------------------------------------------
  85
  86'git-rev-list' is a very essential git program, since it
  87provides the ability to build and traverse commit ancestry graphs. For
  88this reason, it has a lot of different options that enables it to be
  89used by commands as different as 'git-bisect' and
  90'git-repack'.
  91
  92OPTIONS
  93-------
  94
  95:git-rev-list: 1
  96include::rev-list-options.txt[]
  97
  98include::pretty-formats.txt[]
  99
 100
 101Author
 102------
 103Written by Linus Torvalds <torvalds@osdl.org>
 104
 105Documentation
 106--------------
 107Documentation by David Greaves, Junio C Hamano, Jonas Fonseca
 108and the git-list <git@vger.kernel.org>.
 109
 110GIT
 111---
 112Part of the linkgit:git[1] suite