rev-parse --glob
[git/git.git] / 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 [ \--merges ]
18 [ \--no-merges ]
19 [ \--first-parent ]
20 [ \--remove-empty ]
21 [ \--full-history ]
22 [ \--not ]
23 [ \--all ]
24 [ \--branches ]
25 [ \--tags ]
26 [ \--remotes ]
27 [ \--glob=glob-pattern ]
28 [ \--stdin ]
29 [ \--quiet ]
30 [ \--topo-order ]
31 [ \--parents ]
32 [ \--timestamp ]
33 [ \--left-right ]
34 [ \--cherry-pick ]
35 [ \--encoding[=<encoding>] ]
36 [ \--(author|committer|grep)=<pattern> ]
37 [ \--regexp-ignore-case | -i ]
38 [ \--extended-regexp | -E ]
39 [ \--fixed-strings | -F ]
40 [ \--date={local|relative|default|iso|rfc|short} ]
41 [ [\--objects | \--objects-edge] [ \--unpacked ] ]
42 [ \--pretty | \--header ]
43 [ \--bisect ]
44 [ \--bisect-vars ]
45 [ \--bisect-all ]
46 [ \--merge ]
47 [ \--reverse ]
48 [ \--walk-reflogs ]
49 [ \--no-walk ] [ \--do-walk ]
50 <commit>... [ \-- <paths>... ]
51
52 DESCRIPTION
53 -----------
54
55 List commits that are reachable by following the `parent` links from the
56 given commit(s), but exclude commits that are reachable from the one(s)
57 given with a '{caret}' in front of them. The output is given in reverse
58 chronological order by default.
59
60 You can think of this as a set operation. Commits given on the command
61 line form a set of commits that are reachable from any of them, and then
62 commits reachable from any of the ones given with '{caret}' in front are
63 subtracted from that set. The remaining commits are what comes out in the
64 command's output. Various other options and paths parameters can be used
65 to further limit the result.
66
67 Thus, the following command:
68
69 -----------------------------------------------------------------------
70 $ git rev-list foo bar ^baz
71 -----------------------------------------------------------------------
72
73 means "list all the commits which are reachable from 'foo' or 'bar', but
74 not from 'baz'".
75
76 A special notation "'<commit1>'..'<commit2>'" can be used as a
77 short-hand for "{caret}'<commit1>' '<commit2>'". For example, either of
78 the following may be used interchangeably:
79
80 -----------------------------------------------------------------------
81 $ git rev-list origin..HEAD
82 $ git rev-list HEAD ^origin
83 -----------------------------------------------------------------------
84
85 Another special notation is "'<commit1>'...'<commit2>'" which is useful
86 for merges. The resulting set of commits is the symmetric difference
87 between the two operands. The following two commands are equivalent:
88
89 -----------------------------------------------------------------------
90 $ git rev-list A B --not $(git merge-base --all A B)
91 $ git rev-list A...B
92 -----------------------------------------------------------------------
93
94 'rev-list' is a very essential git command, since it
95 provides the ability to build and traverse commit ancestry graphs. For
96 this reason, it has a lot of different options that enables it to be
97 used by commands as different as 'git-bisect' and
98 'git-repack'.
99
100 OPTIONS
101 -------
102
103 :git-rev-list: 1
104 include::rev-list-options.txt[]
105
106 include::pretty-formats.txt[]
107
108
109 Author
110 ------
111 Written by Linus Torvalds <torvalds@osdl.org>
112
113 Documentation
114 --------------
115 Documentation by David Greaves, Junio C Hamano, Jonas Fonseca
116 and the git-list <git@vger.kernel.org>.
117
118 GIT
119 ---
120 Part of the linkgit:git[1] suite