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