Prevent case sensitive commit
[git/jr.git] / Documentation / git-rev-list.txt
blob5b96eabfce9eecbfccaff16096c616105a040c3d
1 git-rev-list(1)
2 ===============
4 NAME
5 ----
6 git-rev-list - Lists commit objects in reverse chronological order
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              [ \--date={local|relative|default|iso|rfc|short} ]
35              [ [\--objects | \--objects-edge] [ \--unpacked ] ]
36              [ \--pretty | \--header ]
37              [ \--bisect ]
38              [ \--bisect-vars ]
39              [ \--bisect-all ]
40              [ \--merge ]
41              [ \--reverse ]
42              [ \--walk-reflogs ]
43              [ \--no-walk ] [ \--do-walk ]
44              <commit>... [ \-- <paths>... ]
46 DESCRIPTION
47 -----------
49 Lists commit objects in reverse chronological order starting at the
50 given commit(s), taking ancestry relationship into account.  This is
51 useful to produce human-readable log output.
53 Commits which are stated with a preceding '{caret}' cause listing to
54 stop at that point. Their parents are implied. Thus the following
55 command:
57 -----------------------------------------------------------------------
58         $ git-rev-list foo bar ^baz
59 -----------------------------------------------------------------------
61 means "list all the commits which are included in 'foo' and 'bar', but
62 not in 'baz'".
64 A special notation "'<commit1>'..'<commit2>'" can be used as a
65 short-hand for "{caret}'<commit1>' '<commit2>'". For example, either of
66 the following may be used interchangeably:
68 -----------------------------------------------------------------------
69         $ git-rev-list origin..HEAD
70         $ git-rev-list HEAD ^origin
71 -----------------------------------------------------------------------
73 Another special notation is "'<commit1>'...'<commit2>'" which is useful
74 for merges.  The resulting set of commits is the symmetric difference
75 between the two operands.  The following two commands are equivalent:
77 -----------------------------------------------------------------------
78         $ git-rev-list A B --not $(git-merge-base --all A B)
79         $ git-rev-list A...B
80 -----------------------------------------------------------------------
82 linkgit:git-rev-list[1] is a very essential git program, since it
83 provides the ability to build and traverse commit ancestry graphs. For
84 this reason, it has a lot of different options that enables it to be
85 used by commands as different as linkgit:git-bisect[1] and
86 linkgit:git-repack[1].
88 OPTIONS
89 -------
91 :git-rev-list: 1
92 include::rev-list-options.txt[]
94 include::pretty-formats.txt[]
97 Author
98 ------
99 Written by Linus Torvalds <torvalds@osdl.org>
101 Documentation
102 --------------
103 Documentation by David Greaves, Junio C Hamano, Jonas Fonseca
104 and the git-list <git@vger.kernel.org>.
108 Part of the linkgit:git[7] suite