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 [ \--remove-empty ]
19 [ \--full-history ]
20 [ \--not ]
21 [ \--all ]
22 [ \--stdin ]
23 [ \--topo-order ]
24 [ \--parents ]
25 [ \--left-right ]
26 [ \--cherry-pick ]
27 [ \--encoding[=<encoding>] ]
28 [ \--(author|committer|grep)=<pattern> ]
29 [ \--regexp-ignore-case ] [ \--extended-regexp ]
30 [ \--date={local|relative|default} ]
31 [ [\--objects | \--objects-edge] [ \--unpacked ] ]
32 [ \--pretty | \--header ]
33 [ \--bisect ]
34 [ \--bisect-vars ]
35 [ \--merge ]
36 [ \--reverse ]
37 [ \--walk-reflogs ]
38 <commit>... [ \-- <paths>... ]
40 DESCRIPTION
41 -----------
43 Lists commit objects in reverse chronological order starting at the
44 given commit(s), taking ancestry relationship into account. This is
45 useful to produce human-readable log output.
47 Commits which are stated with a preceding '{caret}' cause listing to
48 stop at that point. Their parents are implied. Thus the following
49 command:
51 -----------------------------------------------------------------------
52 $ git-rev-list foo bar ^baz
53 -----------------------------------------------------------------------
55 means "list all the commits which are included in 'foo' and 'bar', but
56 not in 'baz'".
58 A special notation "'<commit1>'..'<commit2>'" can be used as a
59 short-hand for "{caret}'<commit1>' '<commit2>'". For example, either of
60 the following may be used interchangeably:
62 -----------------------------------------------------------------------
63 $ git-rev-list origin..HEAD
64 $ git-rev-list HEAD ^origin
65 -----------------------------------------------------------------------
67 Another special notation is "'<commit1>'...'<commit2>'" which is useful
68 for merges. The resulting set of commits is the symmetric difference
69 between the two operands. The following two commands are equivalent:
71 -----------------------------------------------------------------------
72 $ git-rev-list A B --not $(git-merge-base --all A B)
73 $ git-rev-list A...B
74 -----------------------------------------------------------------------
76 gitlink:git-rev-list[1] is a very essential git program, since it
77 provides the ability to build and traverse commit ancestry graphs. For
78 this reason, it has a lot of different options that enables it to be
79 used by commands as different as gitlink:git-bisect[1] and
80 gitlink:git-repack[1].
82 OPTIONS
83 -------
85 Commit Formatting
86 ~~~~~~~~~~~~~~~~~
88 Using these options, gitlink:git-rev-list[1] will act similar to the
89 more specialized family of commit log tools: gitlink:git-log[1],
90 gitlink:git-show[1], and gitlink:git-whatchanged[1]
92 include::pretty-options.txt[]
94 --relative-date::
96 Synonym for `--date=relative`.
98 --date={relative,local,default}::
100 Only takes effect for dates shown in human-readable format, such
101 as when using "--pretty".
102 +
103 `--date=relative` shows dates relative to the current time,
104 e.g. "2 hours ago".
105 +
106 `--date=local` shows timestamps in user's local timezone.
107 +
108 `--date=default` shows timestamps in the original timezone
109 (either committer's or author's).
111 --header::
113 Print the contents of the commit in raw-format; each record is
114 separated with a NUL character.
116 --parents::
118 Print the parents of the commit.
120 --left-right::
122 Mark which side of a symmetric diff a commit is reachable from.
123 Commits from the left side are prefixed with `<` and those from
124 the right with `>`. If combined with `--boundary`, those
125 commits are prefixed with `-`.
126 +
127 For example, if you have this topology:
128 +
129 -----------------------------------------------------------------------
130 y---b---b branch B
131 / \ /
132 / .
133 / / \
134 o---x---a---a branch A
135 -----------------------------------------------------------------------
136 +
137 you would get an output line this:
138 +
139 -----------------------------------------------------------------------
140 $ git rev-list --left-right --boundary --pretty=oneline A...B
142 >bbbbbbb... 3rd on b
143 >bbbbbbb... 2nd on b
144 <aaaaaaa... 3rd on a
145 <aaaaaaa... 2nd on a
146 -yyyyyyy... 1st on b
147 -xxxxxxx... 1st on a
148 -----------------------------------------------------------------------
150 Diff Formatting
151 ~~~~~~~~~~~~~~~
153 Below are listed options that control the formatting of diff output.
154 Some of them are specific to gitlink:git-rev-list[1], however other diff
155 options may be given. See gitlink:git-diff-files[1] for more options.
157 -c::
159 This flag changes the way a merge commit is displayed. It shows
160 the differences from each of the parents to the merge result
161 simultaneously instead of showing pairwise diff between a parent
162 and the result one at a time. Furthermore, it lists only files
163 which were modified from all parents.
165 --cc::
167 This flag implies the '-c' options and further compresses the
168 patch output by omitting hunks that show differences from only
169 one parent, or show the same change from all but one parent for
170 an Octopus merge.
172 -r::
174 Show recursive diffs.
176 -t::
178 Show the tree objects in the diff output. This implies '-r'.
180 Commit Limiting
181 ~~~~~~~~~~~~~~~
183 Besides specifying a range of commits that should be listed using the
184 special notations explained in the description, additional commit
185 limiting may be applied.
187 --
189 -n 'number', --max-count='number'::
191 Limit the number of commits output.
193 --skip='number'::
195 Skip 'number' commits before starting to show the commit output.
197 --since='date', --after='date'::
199 Show commits more recent than a specific date.
201 --until='date', --before='date'::
203 Show commits older than a specific date.
205 --max-age='timestamp', --min-age='timestamp'::
207 Limit the commits output to specified time range.
209 --author='pattern', --committer='pattern'::
211 Limit the commits output to ones with author/committer
212 header lines that match the specified pattern (regular expression).
214 --grep='pattern'::
216 Limit the commits output to ones with log message that
217 matches the specified pattern (regular expression).
219 --regexp-ignore-case::
221 Match the regexp limiting patterns without regard to letters case.
223 --extended-regexp::
225 Consider the limiting patterns to be extended regular expressions
226 instead of the default basic regular expressions.
228 --remove-empty::
230 Stop when a given path disappears from the tree.
232 --full-history::
234 Show also parts of history irrelevant to current state of a given
235 path. This turns off history simplification, which removed merges
236 which didn't change anything at all at some child. It will still actually
237 simplify away merges that didn't change anything at all into either
238 child.
240 --no-merges::
242 Do not print commits with more than one parent.
244 --not::
246 Reverses the meaning of the '{caret}' prefix (or lack thereof)
247 for all following revision specifiers, up to the next '--not'.
249 --all::
251 Pretend as if all the refs in `$GIT_DIR/refs/` are listed on the
252 command line as '<commit>'.
254 --stdin::
256 In addition to the '<commit>' listed on the command
257 line, read them from the standard input.
259 --cherry-pick::
261 Omit any commit that introduces the same change as
262 another commit on the "other side" when the set of
263 commits are limited with symmetric difference.
264 +
265 For example, if you have two branches, `A` and `B`, a usual way
266 to list all commits on only one side of them is with
267 `--left-right`, like the example above in the description of
268 that option. It however shows the commits that were cherry-picked
269 from the other branch (for example, "3rd on b" may be cherry-picked
270 from branch A). With this option, such pairs of commits are
271 excluded from the output.
273 -g, --walk-reflogs::
275 Instead of walking the commit ancestry chain, walk
276 reflog entries from the most recent one to older ones.
277 When this option is used you cannot specify commits to
278 exclude (that is, '{caret}commit', 'commit1..commit2',
279 nor 'commit1...commit2' notations cannot be used).
280 +
281 With '\--pretty' format other than oneline (for obvious reasons),
282 this causes the output to have two extra lines of information
283 taken from the reflog. By default, 'commit@{Nth}' notation is
284 used in the output. When the starting commit is specified as
285 'commit@{now}', output also uses 'commit@{timestamp}' notation
286 instead. Under '\--pretty=oneline', the commit message is
287 prefixed with this information on the same line.
289 --merge::
291 After a failed merge, show refs that touch files having a
292 conflict and don't exist on all heads to merge.
294 --boundary::
296 Output uninteresting commits at the boundary, which are usually
297 not shown.
299 --dense, --sparse::
301 When optional paths are given, the default behaviour ('--dense') is to
302 only output commits that changes at least one of them, and also ignore
303 merges that do not touch the given paths.
305 Use the '--sparse' flag to makes the command output all eligible commits
306 (still subject to count and age limitation), but apply merge
307 simplification nevertheless.
309 --bisect::
311 Limit output to the one commit object which is roughly halfway between
312 the included and excluded commits. Thus, if
314 -----------------------------------------------------------------------
315 $ git-rev-list --bisect foo ^bar ^baz
316 -----------------------------------------------------------------------
318 outputs 'midpoint', the output of the two commands
320 -----------------------------------------------------------------------
321 $ git-rev-list foo ^midpoint
322 $ git-rev-list midpoint ^bar ^baz
323 -----------------------------------------------------------------------
325 would be of roughly the same length. Finding the change which
326 introduces a regression is thus reduced to a binary search: repeatedly
327 generate and test new 'midpoint's until the commit chain is of length
328 one.
330 --bisect-vars::
332 This calculates the same as `--bisect`, but outputs text ready
333 to be eval'ed by the shell. These lines will assign the name of
334 the midpoint revision to the variable `bisect_rev`, and the
335 expected number of commits to be tested after `bisect_rev` is
336 tested to `bisect_nr`, the expected number of commits to be
337 tested if `bisect_rev` turns out to be good to `bisect_good`,
338 the expected number of commits to be tested if `bisect_rev`
339 turns out to be bad to `bisect_bad`, and the number of commits
340 we are bisecting right now to `bisect_all`.
342 --
344 Commit Ordering
345 ~~~~~~~~~~~~~~~
347 By default, the commits are shown in reverse chronological order.
349 --topo-order::
351 This option makes them appear in topological order (i.e.
352 descendant commits are shown before their parents).
354 --date-order::
356 This option is similar to '--topo-order' in the sense that no
357 parent comes before all of its children, but otherwise things
358 are still ordered in the commit timestamp order.
360 --reverse::
362 Output the commits in reverse order.
364 Object Traversal
365 ~~~~~~~~~~~~~~~~
367 These options are mostly targeted for packing of git repositories.
369 --objects::
371 Print the object IDs of any object referenced by the listed
372 commits. 'git-rev-list --objects foo ^bar' thus means "send me
373 all object IDs which I need to download if I have the commit
374 object 'bar', but not 'foo'".
376 --objects-edge::
378 Similar to '--objects', but also print the IDs of excluded
379 commits prefixed with a "-" character. This is used by
380 gitlink:git-pack-objects[1] to build "thin" pack, which records
381 objects in deltified form based on objects contained in these
382 excluded commits to reduce network traffic.
384 --unpacked::
386 Only useful with '--objects'; print the object IDs that are not
387 in packs.
390 include::pretty-formats.txt[]
393 Author
394 ------
395 Written by Linus Torvalds <torvalds@osdl.org>
397 Documentation
398 --------------
399 Documentation by David Greaves, Junio C Hamano, Jonas Fonseca
400 and the git-list <git@vger.kernel.org>.
402 GIT
403 ---
404 Part of the gitlink:git[7] suite