Documentation/git-rev-list.txt

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