]>
Commit | Line | Data |
---|---|---|
fdcf39e5 MV |
1 | Commit Limiting |
2 | ~~~~~~~~~~~~~~~ | |
3 | ||
4 | Besides specifying a range of commits that should be listed using the | |
5 | special notations explained in the description, additional commit | |
a23e3138 JH |
6 | limiting may be applied. |
7 | ||
8 | Using more options generally further limits the output (e.g. | |
9 | `--since=<date1>` limits to commits newer than `<date1>`, and using it | |
10 | with `--grep=<pattern>` further limits to commits whose log message | |
11 | has a line that matches `<pattern>`), unless otherwise noted. | |
12 | ||
13 | Note that these are applied before commit | |
14 | ordering and formatting options, such as `--reverse`. | |
fdcf39e5 MV |
15 | |
16 | -- | |
17 | ||
70c2a258 NTND |
18 | -<number>:: |
19 | -n <number>:: | |
982962ce | 20 | --max-count=<number>:: |
841d8118 | 21 | Limit the number of commits to output. |
fdcf39e5 | 22 | |
982962ce | 23 | --skip=<number>:: |
fdcf39e5 MV |
24 | Skip 'number' commits before starting to show the commit output. |
25 | ||
982962ce MM |
26 | --since=<date>:: |
27 | --after=<date>:: | |
fdcf39e5 MV |
28 | Show commits more recent than a specific date. |
29 | ||
982962ce MM |
30 | --until=<date>:: |
31 | --before=<date>:: | |
fdcf39e5 MV |
32 | Show commits older than a specific date. |
33 | ||
56b6d01d | 34 | ifdef::git-rev-list[] |
982962ce MM |
35 | --max-age=<timestamp>:: |
36 | --min-age=<timestamp>:: | |
fdcf39e5 | 37 | Limit the commits output to specified time range. |
56b6d01d | 38 | endif::git-rev-list[] |
fdcf39e5 | 39 | |
982962ce MM |
40 | --author=<pattern>:: |
41 | --committer=<pattern>:: | |
fdcf39e5 | 42 | Limit the commits output to ones with author/committer |
a23e3138 JH |
43 | header lines that match the specified pattern (regular |
44 | expression). With more than one `--author=<pattern>`, | |
45 | commits whose author matches any of the given patterns are | |
46 | chosen (similarly for multiple `--committer=<pattern>`). | |
fdcf39e5 | 47 | |
72fd13f7 | 48 | --grep-reflog=<pattern>:: |
72fd13f7 NTND |
49 | Limit the commits output to ones with reflog entries that |
50 | match the specified pattern (regular expression). With | |
51 | more than one `--grep-reflog`, commits whose reflog message | |
baa6378f JH |
52 | matches any of the given patterns are chosen. It is an |
53 | error to use this option unless `--walk-reflogs` is in use. | |
72fd13f7 | 54 | |
982962ce | 55 | --grep=<pattern>:: |
fdcf39e5 | 56 | Limit the commits output to ones with log message that |
a23e3138 JH |
57 | matches the specified pattern (regular expression). With |
58 | more than one `--grep=<pattern>`, commits whose message | |
59 | matches any of the given patterns are chosen (but see | |
60 | `--all-match`). | |
38cfe915 NTND |
61 | + |
62 | When `--show-notes` is in effect, the message from the notes as | |
63 | if it is part of the log message. | |
fdcf39e5 | 64 | |
7756ba74 | 65 | --all-match:: |
4528aa1a | 66 | Limit the commits output to ones that match all given `--grep`, |
a23e3138 | 67 | instead of ones that match at least one. |
7756ba74 | 68 | |
3240240f SB |
69 | -i:: |
70 | --regexp-ignore-case:: | |
19d6eb41 JSJ |
71 | Match the regular expression limiting patterns without regard to letter |
72 | case. | |
fdcf39e5 | 73 | |
727b6fc3 | 74 | --basic-regexp:: |
727b6fc3 JH |
75 | Consider the limiting patterns to be basic regular expressions; |
76 | this is the default. | |
77 | ||
3240240f SB |
78 | -E:: |
79 | --extended-regexp:: | |
fdcf39e5 MV |
80 | Consider the limiting patterns to be extended regular expressions |
81 | instead of the default basic regular expressions. | |
82 | ||
3240240f SB |
83 | -F:: |
84 | --fixed-strings:: | |
dc1c0fff JN |
85 | Consider the limiting patterns to be fixed strings (don't interpret |
86 | pattern as a regular expression). | |
87 | ||
727b6fc3 | 88 | --perl-regexp:: |
19d6eb41 | 89 | Consider the limiting patterns to be Perl-compatible regular expressions. |
727b6fc3 JH |
90 | Requires libpcre to be compiled in. |
91 | ||
fdcf39e5 | 92 | --remove-empty:: |
fdcf39e5 MV |
93 | Stop when a given path disappears from the tree. |
94 | ||
2657420d | 95 | --merges:: |
6a6ebded | 96 | Print only merge commits. This is exactly the same as `--min-parents=2`. |
2657420d | 97 | |
fdcf39e5 | 98 | --no-merges:: |
6a6ebded MG |
99 | Do not print commits with more than one parent. This is |
100 | exactly the same as `--max-parents=1`. | |
101 | ||
102 | --min-parents=<number>:: | |
103 | --max-parents=<number>:: | |
104 | --no-min-parents:: | |
105 | --no-max-parents:: | |
5104d21f | 106 | Show only commits which have at least (or at most) that many parent |
6a6ebded MG |
107 | commits. In particular, `--max-parents=1` is the same as `--no-merges`, |
108 | `--min-parents=2` is the same as `--merges`. `--max-parents=0` | |
109 | gives all root commits and `--min-parents=3` all octopus merges. | |
110 | + | |
111 | `--no-min-parents` and `--no-max-parents` reset these limits (to no limit) | |
112 | again. Equivalent forms are `--min-parents=0` (any commit has 0 or more | |
113 | parents) and `--max-parents=-1` (negative numbers denote no upper limit). | |
fdcf39e5 MV |
114 | |
115 | --first-parent:: | |
116 | Follow only the first parent commit upon seeing a merge | |
117 | commit. This option can give a better overview when | |
118 | viewing the evolution of a particular topic branch, | |
119 | because merges into a topic branch tend to be only about | |
120 | adjusting to updated upstream from time to time, and | |
121 | this option allows you to ignore the individual commits | |
122 | brought in to your history by such a merge. | |
123 | ||
124 | --not:: | |
fdcf39e5 | 125 | Reverses the meaning of the '{caret}' prefix (or lack thereof) |
4528aa1a | 126 | for all following revision specifiers, up to the next `--not`. |
fdcf39e5 MV |
127 | |
128 | --all:: | |
cc1b8d8b | 129 | Pretend as if all the refs in `refs/` are listed on the |
fdcf39e5 | 130 | command line as '<commit>'. |
c2e6385d | 131 | |
62b4698e | 132 | --branches[=<pattern>]:: |
cc1b8d8b | 133 | Pretend as if all the refs in `refs/heads` are listed |
62b4698e | 134 | on the command line as '<commit>'. If '<pattern>' is given, limit |
b09fe971 | 135 | branches to ones matching given shell glob. If pattern lacks '?', |
e34bb2e7 | 136 | '{asterisk}', or '[', '/{asterisk}' at the end is implied. |
c2e6385d | 137 | |
62b4698e | 138 | --tags[=<pattern>]:: |
cc1b8d8b | 139 | Pretend as if all the refs in `refs/tags` are listed |
62b4698e | 140 | on the command line as '<commit>'. If '<pattern>' is given, limit |
e34bb2e7 CMN |
141 | tags to ones matching given shell glob. If pattern lacks '?', '{asterisk}', |
142 | or '[', '/{asterisk}' at the end is implied. | |
c2e6385d | 143 | |
62b4698e | 144 | --remotes[=<pattern>]:: |
cc1b8d8b | 145 | Pretend as if all the refs in `refs/remotes` are listed |
62b4698e | 146 | on the command line as '<commit>'. If '<pattern>' is given, limit |
0e615b25 | 147 | remote-tracking branches to ones matching given shell glob. |
e34bb2e7 | 148 | If pattern lacks '?', '{asterisk}', or '[', '/{asterisk}' at the end is implied. |
fdcf39e5 | 149 | |
62b4698e ŠN |
150 | --glob=<glob-pattern>:: |
151 | Pretend as if all the refs matching shell glob '<glob-pattern>' | |
d08bae7e | 152 | are listed on the command line as '<commit>'. Leading 'refs/', |
e34bb2e7 CMN |
153 | is automatically prepended if missing. If pattern lacks '?', '{asterisk}', |
154 | or '[', '/{asterisk}' at the end is implied. | |
d08bae7e | 155 | |
574d370b JS |
156 | --exclude=<glob-pattern>:: |
157 | ||
158 | Do not include refs matching '<glob-pattern>' that the next `--all`, | |
159 | `--branches`, `--tags`, `--remotes`, or `--glob` would otherwise | |
160 | consider. Repetitions of this option accumulate exclusion patterns | |
161 | up to the next `--all`, `--branches`, `--tags`, `--remotes`, or | |
162 | `--glob` option (other options or arguments do not clear | |
163 | accumlated patterns). | |
164 | + | |
165 | The patterns given should not begin with `refs/heads`, `refs/tags`, or | |
166 | `refs/remotes` when applied to `--branches`, `--tags`, or `--remotes`, | |
167 | respectively, and they must begin with `refs/` when applied to `--glob` | |
168 | or `--all`. If a trailing '/{asterisk}' is intended, it must be given | |
169 | explicitly. | |
170 | ||
cc243c3c | 171 | --ignore-missing:: |
cc243c3c JH |
172 | Upon seeing an invalid object name in the input, pretend as if |
173 | the bad input was not given. | |
d08bae7e | 174 | |
af06e93a CC |
175 | ifndef::git-rev-list[] |
176 | --bisect:: | |
cc1b8d8b | 177 | Pretend as if the bad bisection ref `refs/bisect/bad` |
af06e93a | 178 | was listed and as if it was followed by `--not` and the good |
cc1b8d8b | 179 | bisection refs `refs/bisect/good-*` on the command |
af06e93a CC |
180 | line. |
181 | endif::git-rev-list[] | |
182 | ||
fdcf39e5 | 183 | --stdin:: |
fdcf39e5 | 184 | In addition to the '<commit>' listed on the command |
60da8b15 JH |
185 | line, read them from the standard input. If a '--' separator is |
186 | seen, stop reading commits and start reading paths to limit the | |
187 | result. | |
fdcf39e5 | 188 | |
8b3dce56 | 189 | ifdef::git-rev-list[] |
fdcf39e5 | 190 | --quiet:: |
fdcf39e5 MV |
191 | Don't print anything to standard output. This form |
192 | is primarily meant to allow the caller to | |
193 | test the exit status to see if a range of objects is fully | |
194 | connected (or not). It is faster than redirecting stdout | |
4528aa1a | 195 | to `/dev/null` as the output does not have to be formatted. |
adf60f14 | 196 | endif::git-rev-list[] |
fdcf39e5 | 197 | |
cb56e309 | 198 | --cherry-mark:: |
cb56e309 MG |
199 | Like `--cherry-pick` (see below) but mark equivalent commits |
200 | with `=` rather than omitting them, and inequivalent ones with `+`. | |
201 | ||
fdcf39e5 | 202 | --cherry-pick:: |
fdcf39e5 | 203 | Omit any commit that introduces the same change as |
4528aa1a | 204 | another commit on the ``other side'' when the set of |
fdcf39e5 MV |
205 | commits are limited with symmetric difference. |
206 | + | |
207 | For example, if you have two branches, `A` and `B`, a usual way | |
208 | to list all commits on only one side of them is with | |
3add01bb | 209 | `--left-right` (see the example below in the description of |
19d6eb41 JSJ |
210 | the `--left-right` option). However, it shows the commits that were |
211 | cherry-picked from the other branch (for example, ``3rd on b'' may be | |
212 | cherry-picked from branch A). With this option, such pairs of commits are | |
fdcf39e5 MV |
213 | excluded from the output. |
214 | ||
59c8afdf MG |
215 | --left-only:: |
216 | --right-only:: | |
59c8afdf MG |
217 | List only commits on the respective side of a symmetric range, |
218 | i.e. only those which would be marked `<` resp. `>` by | |
219 | `--left-right`. | |
220 | + | |
221 | For example, `--cherry-pick --right-only A...B` omits those | |
222 | commits from `B` which are in `A` or are patch-equivalent to a commit in | |
6cf378f0 | 223 | `A`. In other words, this lists the `+` commits from `git cherry A B`. |
59c8afdf MG |
224 | More precisely, `--cherry-pick --right-only --no-merges` gives the exact |
225 | list. | |
226 | ||
94f605ec | 227 | --cherry:: |
94f605ec MG |
228 | A synonym for `--right-only --cherry-mark --no-merges`; useful to |
229 | limit the output to the commits on our side and mark those that | |
230 | have been applied to the other side of a forked history with | |
231 | `git log --cherry upstream...mybranch`, similar to | |
232 | `git cherry upstream mybranch`. | |
233 | ||
3240240f SB |
234 | -g:: |
235 | --walk-reflogs:: | |
fdcf39e5 MV |
236 | Instead of walking the commit ancestry chain, walk |
237 | reflog entries from the most recent one to older ones. | |
238 | When this option is used you cannot specify commits to | |
239 | exclude (that is, '{caret}commit', 'commit1..commit2', | |
a58088ab | 240 | and 'commit1\...commit2' notations cannot be used). |
fdcf39e5 | 241 | + |
4528aa1a | 242 | With `--pretty` format other than `oneline` (for obvious reasons), |
fdcf39e5 MV |
243 | this causes the output to have two extra lines of information |
244 | taken from the reflog. By default, 'commit@\{Nth}' notation is | |
245 | used in the output. When the starting commit is specified as | |
18a2197e | 246 | 'commit@\{now}', output also uses 'commit@\{timestamp}' notation |
4528aa1a | 247 | instead. Under `--pretty=oneline`, the commit message is |
fdcf39e5 | 248 | prefixed with this information on the same line. |
4528aa1a | 249 | This option cannot be combined with `--reverse`. |
fdcf39e5 MV |
250 | See also linkgit:git-reflog[1]. |
251 | ||
252 | --merge:: | |
fdcf39e5 MV |
253 | After a failed merge, show refs that touch files having a |
254 | conflict and don't exist on all heads to merge. | |
255 | ||
256 | --boundary:: | |
e32db66d KB |
257 | Output excluded boundary commits. Boundary commits are |
258 | prefixed with `-`. | |
fdcf39e5 | 259 | |
aa32939f VM |
260 | ifdef::git-rev-list[] |
261 | --use-bitmap-index:: | |
262 | ||
263 | Try to speed up the traversal using the pack bitmap index (if | |
264 | one is available). Note that when traversing with `--objects`, | |
265 | trees and blobs will not have their associated path printed. | |
266 | endif::git-rev-list[] | |
267 | ||
70d9895e TR |
268 | -- |
269 | ||
270 | History Simplification | |
271 | ~~~~~~~~~~~~~~~~~~~~~~ | |
272 | ||
7bc2508b SB |
273 | Sometimes you are only interested in parts of the history, for example the |
274 | commits modifying a particular <path>. But there are two parts of | |
275 | 'History Simplification', one part is selecting the commits and the other | |
276 | is how to do it, as there are various strategies to simplify the history. | |
277 | ||
278 | The following options select the commits to be shown: | |
279 | ||
280 | <paths>:: | |
7bc2508b SB |
281 | Commits modifying the given <paths> are selected. |
282 | ||
283 | --simplify-by-decoration:: | |
7bc2508b SB |
284 | Commits that are referred by some branch or tag are selected. |
285 | ||
286 | Note that extra commits can be shown to give a meaningful history. | |
287 | ||
288 | The following options affect the way the simplification is performed: | |
289 | ||
290 | Default mode:: | |
7bc2508b SB |
291 | Simplifies the history to the simplest history explaining the |
292 | final state of the tree. Simplest because it prunes some side | |
293 | branches if the end result is the same (i.e. merging branches | |
294 | with the same content) | |
295 | ||
296 | --full-history:: | |
df6b0cad | 297 | Same as the default mode, but does not prune some history. |
7bc2508b SB |
298 | |
299 | --dense:: | |
7bc2508b SB |
300 | Only the selected commits are shown, plus some to have a |
301 | meaningful history. | |
302 | ||
303 | --sparse:: | |
7bc2508b SB |
304 | All commits in the simplified history are shown. |
305 | ||
306 | --simplify-merges:: | |
4528aa1a | 307 | Additional option to `--full-history` to remove some needless |
7bc2508b SB |
308 | merges from the resulting history, as there are no selected |
309 | commits contributing to this merge. | |
310 | ||
57456ef4 | 311 | --ancestry-path:: |
57456ef4 JH |
312 | When given a range of commits to display (e.g. 'commit1..commit2' |
313 | or 'commit2 {caret}commit1'), only display commits that exist | |
314 | directly on the ancestry chain between the 'commit1' and | |
315 | 'commit2', i.e. commits that are both descendants of 'commit1', | |
316 | and ancestors of 'commit2'. | |
317 | ||
7bc2508b | 318 | A more detailed explanation follows. |
70d9895e TR |
319 | |
320 | Suppose you specified `foo` as the <paths>. We shall call commits | |
321 | that modify `foo` !TREESAME, and the rest TREESAME. (In a diff | |
322 | filtered for `foo`, they look different and equal, respectively.) | |
323 | ||
324 | In the following, we will always refer to the same example history to | |
325 | illustrate the differences between simplification settings. We assume | |
326 | that you are filtering for a file `foo` in this commit graph: | |
327 | ----------------------------------------------------------------------- | |
143f1eaf KB |
328 | .-A---M---N---O---P---Q |
329 | / / / / / / | |
330 | I B C D E Y | |
331 | \ / / / / / | |
332 | `-------------' X | |
70d9895e | 333 | ----------------------------------------------------------------------- |
143f1eaf | 334 | The horizontal line of history A---Q is taken to be the first parent of |
70d9895e TR |
335 | each merge. The commits are: |
336 | ||
337 | * `I` is the initial commit, in which `foo` exists with contents | |
4528aa1a | 338 | ``asdf'', and a file `quux` exists with contents ``quux''. Initial |
70d9895e TR |
339 | commits are compared to an empty tree, so `I` is !TREESAME. |
340 | ||
4528aa1a | 341 | * In `A`, `foo` contains just ``foo''. |
70d9895e TR |
342 | |
343 | * `B` contains the same change as `A`. Its merge `M` is trivial and | |
344 | hence TREESAME to all parents. | |
345 | ||
4528aa1a | 346 | * `C` does not change `foo`, but its merge `N` changes it to ``foobar'', |
70d9895e TR |
347 | so it is not TREESAME to any parent. |
348 | ||
4528aa1a JSJ |
349 | * `D` sets `foo` to ``baz''. Its merge `O` combines the strings from |
350 | `N` and `D` to ``foobarbaz''; i.e., it is not TREESAME to any parent. | |
70d9895e | 351 | |
4528aa1a JSJ |
352 | * `E` changes `quux` to ``xyzzy'', and its merge `P` combines the |
353 | strings to ``quux xyzzy''. `P` is TREESAME to `O`, but not to `E`. | |
70d9895e | 354 | |
17b83d71 | 355 | * `X` is an independent root commit that added a new file `side`, and `Y` |
143f1eaf KB |
356 | modified it. `Y` is TREESAME to `X`. Its merge `Q` added `side` to `P`, and |
357 | `Q` is TREESAME to `P`, but not to `Y`. | |
358 | ||
4528aa1a JSJ |
359 | `rev-list` walks backwards through history, including or excluding |
360 | commits based on whether `--full-history` and/or parent rewriting | |
361 | (via `--parents` or `--children`) are used. The following settings | |
70d9895e TR |
362 | are available. |
363 | ||
364 | Default mode:: | |
70d9895e | 365 | Commits are included if they are not TREESAME to any parent |
4528aa1a | 366 | (though this can be changed, see `--sparse` below). If the |
70d9895e TR |
367 | commit was a merge, and it was TREESAME to one parent, follow |
368 | only that parent. (Even if there are several TREESAME | |
369 | parents, follow only one of them.) Otherwise, follow all | |
370 | parents. | |
371 | + | |
372 | This results in: | |
373 | + | |
374 | ----------------------------------------------------------------------- | |
375 | .-A---N---O | |
f70d0586 | 376 | / / / |
70d9895e TR |
377 | I---------D |
378 | ----------------------------------------------------------------------- | |
379 | + | |
380 | Note how the rule to only follow the TREESAME parent, if one is | |
381 | available, removed `B` from consideration entirely. `C` was | |
382 | considered via `N`, but is TREESAME. Root commits are compared to an | |
383 | empty tree, so `I` is !TREESAME. | |
384 | + | |
4528aa1a | 385 | Parent/child relations are only visible with `--parents`, but that does |
70d9895e TR |
386 | not affect the commits selected in default mode, so we have shown the |
387 | parent lines. | |
388 | ||
389 | --full-history without parent rewriting:: | |
70d9895e TR |
390 | This mode differs from the default in one point: always follow |
391 | all parents of a merge, even if it is TREESAME to one of them. | |
392 | Even if more than one side of the merge has commits that are | |
393 | included, this does not imply that the merge itself is! In | |
394 | the example, we get | |
395 | + | |
396 | ----------------------------------------------------------------------- | |
143f1eaf | 397 | I A B N D O P Q |
70d9895e TR |
398 | ----------------------------------------------------------------------- |
399 | + | |
d0af663e | 400 | `M` was excluded because it is TREESAME to both parents. `E`, |
70d9895e TR |
401 | `C` and `B` were all walked, but only `B` was !TREESAME, so the others |
402 | do not appear. | |
403 | + | |
404 | Note that without parent rewriting, it is not really possible to talk | |
405 | about the parent/child relationships between the commits, so we show | |
406 | them disconnected. | |
407 | ||
408 | --full-history with parent rewriting:: | |
70d9895e | 409 | Ordinary commits are only included if they are !TREESAME |
4528aa1a | 410 | (though this can be changed, see `--sparse` below). |
70d9895e TR |
411 | + |
412 | Merges are always included. However, their parent list is rewritten: | |
413 | Along each parent, prune away commits that are not included | |
414 | themselves. This results in | |
415 | + | |
416 | ----------------------------------------------------------------------- | |
143f1eaf | 417 | .-A---M---N---O---P---Q |
70d9895e TR |
418 | / / / / / |
419 | I B / D / | |
420 | \ / / / / | |
421 | `-------------' | |
422 | ----------------------------------------------------------------------- | |
423 | + | |
4528aa1a | 424 | Compare to `--full-history` without rewriting above. Note that `E` |
70d9895e TR |
425 | was pruned away because it is TREESAME, but the parent list of P was |
426 | rewritten to contain `E`'s parent `I`. The same happened for `C` and | |
143f1eaf | 427 | `N`, and `X`, `Y` and `Q`. |
70d9895e TR |
428 | |
429 | In addition to the above settings, you can change whether TREESAME | |
430 | affects inclusion: | |
431 | ||
3240240f | 432 | --dense:: |
70d9895e TR |
433 | Commits that are walked are included if they are not TREESAME |
434 | to any parent. | |
435 | ||
3240240f | 436 | --sparse:: |
70d9895e TR |
437 | All commits that are walked are included. |
438 | + | |
4528aa1a | 439 | Note that without `--full-history`, this still simplifies merges: if |
70d9895e TR |
440 | one of the parents is TREESAME, we follow only that one, so the other |
441 | sides of the merge are never walked. | |
fdcf39e5 | 442 | |
d266a988 | 443 | --simplify-merges:: |
d266a988 | 444 | First, build a history graph in the same way that |
4528aa1a | 445 | `--full-history` with parent rewriting does (see above). |
d266a988 TR |
446 | + |
447 | Then simplify each commit `C` to its replacement `C'` in the final | |
448 | history according to the following rules: | |
449 | + | |
450 | -- | |
451 | * Set `C'` to `C`. | |
452 | + | |
453 | * Replace each parent `P` of `C'` with its simplification `P'`. In | |
143f1eaf KB |
454 | the process, drop parents that are ancestors of other parents or that are |
455 | root commits TREESAME to an empty tree, and remove duplicates, but take care | |
456 | to never drop all parents that we are TREESAME to. | |
d266a988 TR |
457 | + |
458 | * If after this parent rewriting, `C'` is a root or merge commit (has | |
459 | zero or >1 parents), a boundary commit, or !TREESAME, it remains. | |
460 | Otherwise, it is replaced with its only parent. | |
461 | -- | |
462 | + | |
463 | The effect of this is best shown by way of comparing to | |
4528aa1a | 464 | `--full-history` with parent rewriting. The example turns into: |
d266a988 TR |
465 | + |
466 | ----------------------------------------------------------------------- | |
467 | .-A---M---N---O | |
468 | / / / | |
469 | I B D | |
470 | \ / / | |
471 | `---------' | |
472 | ----------------------------------------------------------------------- | |
473 | + | |
19d6eb41 | 474 | Note the major differences in `N`, `P`, and `Q` over `--full-history`: |
d266a988 TR |
475 | + |
476 | -- | |
477 | * `N`'s parent list had `I` removed, because it is an ancestor of the | |
478 | other parent `M`. Still, `N` remained because it is !TREESAME. | |
479 | + | |
480 | * `P`'s parent list similarly had `I` removed. `P` was then | |
481 | removed completely, because it had one parent and is TREESAME. | |
143f1eaf KB |
482 | + |
483 | * `Q`'s parent list had `Y` simplified to `X`. `X` was then removed, because it | |
484 | was a TREESAME root. `Q` was then removed completely, because it had one | |
485 | parent and is TREESAME. | |
d266a988 | 486 | -- |
fdcf39e5 | 487 | |
57456ef4 JH |
488 | Finally, there is a fifth simplification mode available: |
489 | ||
490 | --ancestry-path:: | |
57456ef4 | 491 | Limit the displayed commits to those directly on the ancestry |
4528aa1a JSJ |
492 | chain between the ``from'' and ``to'' commits in the given commit |
493 | range. I.e. only display commits that are ancestor of the ``to'' | |
19d6eb41 | 494 | commit and descendants of the ``from'' commit. |
57456ef4 JH |
495 | + |
496 | As an example use case, consider the following commit history: | |
497 | + | |
498 | ----------------------------------------------------------------------- | |
499 | D---E-------F | |
500 | / \ \ | |
501 | B---C---G---H---I---J | |
502 | / \ | |
503 | A-------K---------------L--M | |
504 | ----------------------------------------------------------------------- | |
505 | + | |
506 | A regular 'D..M' computes the set of commits that are ancestors of `M`, | |
507 | but excludes the ones that are ancestors of `D`. This is useful to see | |
508 | what happened to the history leading to `M` since `D`, in the sense | |
4528aa1a | 509 | that ``what does `M` have that did not exist in `D`''. The result in this |
57456ef4 JH |
510 | example would be all the commits, except `A` and `B` (and `D` itself, |
511 | of course). | |
512 | + | |
513 | When we want to find out what commits in `M` are contaminated with the | |
514 | bug introduced by `D` and need fixing, however, we might want to view | |
515 | only the subset of 'D..M' that are actually descendants of `D`, i.e. | |
4528aa1a | 516 | excluding `C` and `K`. This is exactly what the `--ancestry-path` |
57456ef4 JH |
517 | option does. Applied to the 'D..M' range, it results in: |
518 | + | |
519 | ----------------------------------------------------------------------- | |
520 | E-------F | |
521 | \ \ | |
522 | G---H---I---J | |
523 | \ | |
524 | L--M | |
525 | ----------------------------------------------------------------------- | |
526 | ||
4528aa1a | 527 | The `--simplify-by-decoration` option allows you to view only the |
3fcfd662 NS |
528 | big picture of the topology of the history, by omitting commits |
529 | that are not referenced by tags. Commits are marked as !TREESAME | |
530 | (in other words, kept after history simplification rules described | |
531 | above) if (1) they are referenced by tags, or (2) they change the | |
532 | contents of the paths given on the command line. All other | |
533 | commits are marked as TREESAME (subject to be simplified away). | |
534 | ||
fdcf39e5 | 535 | ifdef::git-rev-list[] |
70d9895e TR |
536 | Bisection Helpers |
537 | ~~~~~~~~~~~~~~~~~ | |
538 | ||
fdcf39e5 | 539 | --bisect:: |
4528aa1a JSJ |
540 | Limit output to the one commit object which is roughly halfway between |
541 | included and excluded commits. Note that the bad bisection ref | |
542 | `refs/bisect/bad` is added to the included commits (if it | |
543 | exists) and the good bisection refs `refs/bisect/good-*` are | |
544 | added to the excluded commits (if they exist). Thus, supposing there | |
545 | are no refs in `refs/bisect/`, if | |
546 | + | |
fdcf39e5 | 547 | ----------------------------------------------------------------------- |
6514aa36 | 548 | $ git rev-list --bisect foo ^bar ^baz |
fdcf39e5 | 549 | ----------------------------------------------------------------------- |
4528aa1a | 550 | + |
fdcf39e5 | 551 | outputs 'midpoint', the output of the two commands |
4528aa1a | 552 | + |
fdcf39e5 | 553 | ----------------------------------------------------------------------- |
6514aa36 CC |
554 | $ git rev-list foo ^midpoint |
555 | $ git rev-list midpoint ^bar ^baz | |
fdcf39e5 | 556 | ----------------------------------------------------------------------- |
4528aa1a | 557 | + |
fdcf39e5 MV |
558 | would be of roughly the same length. Finding the change which |
559 | introduces a regression is thus reduced to a binary search: repeatedly | |
560 | generate and test new 'midpoint's until the commit chain is of length | |
561 | one. | |
562 | ||
563 | --bisect-vars:: | |
4528aa1a JSJ |
564 | This calculates the same as `--bisect`, except that refs in |
565 | `refs/bisect/` are not used, and except that this outputs | |
566 | text ready to be eval'ed by the shell. These lines will assign the | |
567 | name of the midpoint revision to the variable `bisect_rev`, and the | |
568 | expected number of commits to be tested after `bisect_rev` is tested | |
569 | to `bisect_nr`, the expected number of commits to be tested if | |
570 | `bisect_rev` turns out to be good to `bisect_good`, the expected | |
571 | number of commits to be tested if `bisect_rev` turns out to be bad to | |
572 | `bisect_bad`, and the number of commits we are bisecting right now to | |
573 | `bisect_all`. | |
fdcf39e5 MV |
574 | |
575 | --bisect-all:: | |
4528aa1a JSJ |
576 | This outputs all the commit objects between the included and excluded |
577 | commits, ordered by their distance to the included and excluded | |
578 | commits. Refs in `refs/bisect/` are not used. The farthest | |
579 | from them is displayed first. (This is the only one displayed by | |
580 | `--bisect`.) | |
3d2d4f96 | 581 | + |
fdcf39e5 MV |
582 | This is useful because it makes it easy to choose a good commit to |
583 | test when you want to avoid to test some of them for some reason (they | |
584 | may not compile for example). | |
3d2d4f96 | 585 | + |
fdcf39e5 MV |
586 | This option can be used along with `--bisect-vars`, in this case, |
587 | after all the sorted commit objects, there will be the same text as if | |
588 | `--bisect-vars` had been used alone. | |
589 | endif::git-rev-list[] | |
590 | ||
fdcf39e5 MV |
591 | |
592 | Commit Ordering | |
593 | ~~~~~~~~~~~~~~~ | |
594 | ||
595 | By default, the commits are shown in reverse chronological order. | |
596 | ||
3f0350cc JH |
597 | --date-order:: |
598 | Show no parents before all of its children are shown, but | |
599 | otherwise show commits in the commit timestamp order. | |
fdcf39e5 | 600 | |
81c6b38b JH |
601 | --author-date-order:: |
602 | Show no parents before all of its children are shown, but | |
603 | otherwise show commits in the author timestamp order. | |
604 | ||
3f0350cc JH |
605 | --topo-order:: |
606 | Show no parents before all of its children are shown, and | |
607 | avoid showing commits on multiple lines of history | |
608 | intermixed. | |
609 | + | |
610 | For example, in a commit history like this: | |
611 | + | |
612 | ---------------------------------------------------------------- | |
fdcf39e5 | 613 | |
3f0350cc JH |
614 | ---1----2----4----7 |
615 | \ \ | |
616 | 3----5----6----8--- | |
fdcf39e5 | 617 | |
3f0350cc JH |
618 | ---------------------------------------------------------------- |
619 | + | |
620 | where the numbers denote the order of commit timestamps, `git | |
621 | rev-list` and friends with `--date-order` show the commits in the | |
622 | timestamp order: 8 7 6 5 4 3 2 1. | |
623 | + | |
624 | With `--topo-order`, they would show 8 6 5 3 7 4 2 1 (or 8 7 4 2 6 5 | |
625 | 3 1); some older commits are shown before newer ones in order to | |
626 | avoid showing the commits from two parallel development track mixed | |
627 | together. | |
fdcf39e5 MV |
628 | |
629 | --reverse:: | |
fdcf39e5 | 630 | Output the commits in reverse order. |
4528aa1a | 631 | Cannot be combined with `--walk-reflogs`. |
fdcf39e5 MV |
632 | |
633 | Object Traversal | |
634 | ~~~~~~~~~~~~~~~~ | |
635 | ||
2de9b711 | 636 | These options are mostly targeted for packing of Git repositories. |
fdcf39e5 MV |
637 | |
638 | --objects:: | |
fdcf39e5 | 639 | Print the object IDs of any object referenced by the listed |
4528aa1a | 640 | commits. `--objects foo ^bar` thus means ``send me |
fdcf39e5 | 641 | all object IDs which I need to download if I have the commit |
4528aa1a | 642 | object _bar_ but not _foo_''. |
fdcf39e5 MV |
643 | |
644 | --objects-edge:: | |
4528aa1a JSJ |
645 | Similar to `--objects`, but also print the IDs of excluded |
646 | commits prefixed with a ``-'' character. This is used by | |
647 | linkgit:git-pack-objects[1] to build ``thin'' pack, which records | |
fdcf39e5 MV |
648 | objects in deltified form based on objects contained in these |
649 | excluded commits to reduce network traffic. | |
650 | ||
651 | --unpacked:: | |
4528aa1a | 652 | Only useful with `--objects`; print the object IDs that are not |
fdcf39e5 MV |
653 | in packs. |
654 | ||
ca92e59e | 655 | --no-walk[=(sorted|unsorted)]:: |
ca92e59e MZ |
656 | Only show the given commits, but do not traverse their ancestors. |
657 | This has no effect if a range is specified. If the argument | |
19d6eb41 | 658 | `unsorted` is given, the commits are shown in the order they were |
4528aa1a | 659 | given on the command line. Otherwise (if `sorted` or no argument |
19d6eb41 | 660 | was given), the commits are shown in reverse chronological order |
ca92e59e | 661 | by commit time. |
fdcf39e5 MV |
662 | |
663 | --do-walk:: | |
4528aa1a | 664 | Overrides a previous `--no-walk`. |
f98fd436 MG |
665 | |
666 | Commit Formatting | |
667 | ~~~~~~~~~~~~~~~~~ | |
668 | ||
669 | ifdef::git-rev-list[] | |
670 | Using these options, linkgit:git-rev-list[1] will act similar to the | |
671 | more specialized family of commit log tools: linkgit:git-log[1], | |
672 | linkgit:git-show[1], and linkgit:git-whatchanged[1] | |
673 | endif::git-rev-list[] | |
674 | ||
675 | include::pretty-options.txt[] | |
676 | ||
677 | --relative-date:: | |
f98fd436 MG |
678 | Synonym for `--date=relative`. |
679 | ||
680 | --date=(relative|local|default|iso|rfc|short|raw):: | |
f98fd436 | 681 | Only takes effect for dates shown in human-readable format, such |
4528aa1a | 682 | as when using `--pretty`. `log.date` config variable sets a default |
19d6eb41 | 683 | value for the log command's `--date` option. |
f98fd436 MG |
684 | + |
685 | `--date=relative` shows dates relative to the current time, | |
4528aa1a | 686 | e.g. ``2 hours ago''. |
f98fd436 | 687 | + |
0ffa154b | 688 | `--date=local` shows timestamps in user's local time zone. |
f98fd436 MG |
689 | + |
690 | `--date=iso` (or `--date=iso8601`) shows timestamps in ISO 8601 format. | |
691 | + | |
692 | `--date=rfc` (or `--date=rfc2822`) shows timestamps in RFC 2822 | |
19d6eb41 | 693 | format, often found in email messages. |
f98fd436 | 694 | + |
19d6eb41 | 695 | `--date=short` shows only the date, but not the time, in `YYYY-MM-DD` format. |
f98fd436 | 696 | + |
2de9b711 | 697 | `--date=raw` shows the date in the internal raw Git format `%s %z` format. |
f98fd436 | 698 | + |
0ffa154b | 699 | `--date=default` shows timestamps in the original time zone |
f98fd436 MG |
700 | (either committer's or author's). |
701 | ||
702 | ifdef::git-rev-list[] | |
703 | --header:: | |
f98fd436 MG |
704 | Print the contents of the commit in raw-format; each record is |
705 | separated with a NUL character. | |
706 | endif::git-rev-list[] | |
707 | ||
708 | --parents:: | |
f98fd436 MG |
709 | Print also the parents of the commit (in the form "commit parent..."). |
710 | Also enables parent rewriting, see 'History Simplification' below. | |
711 | ||
712 | --children:: | |
f98fd436 MG |
713 | Print also the children of the commit (in the form "commit child..."). |
714 | Also enables parent rewriting, see 'History Simplification' below. | |
715 | ||
716 | ifdef::git-rev-list[] | |
717 | --timestamp:: | |
718 | Print the raw commit timestamp. | |
719 | endif::git-rev-list[] | |
720 | ||
721 | --left-right:: | |
f98fd436 MG |
722 | Mark which side of a symmetric diff a commit is reachable from. |
723 | Commits from the left side are prefixed with `<` and those from | |
724 | the right with `>`. If combined with `--boundary`, those | |
725 | commits are prefixed with `-`. | |
726 | + | |
727 | For example, if you have this topology: | |
728 | + | |
729 | ----------------------------------------------------------------------- | |
730 | y---b---b branch B | |
731 | / \ / | |
732 | / . | |
733 | / / \ | |
734 | o---x---a---a branch A | |
735 | ----------------------------------------------------------------------- | |
736 | + | |
737 | you would get an output like this: | |
738 | + | |
739 | ----------------------------------------------------------------------- | |
740 | $ git rev-list --left-right --boundary --pretty=oneline A...B | |
741 | ||
742 | >bbbbbbb... 3rd on b | |
743 | >bbbbbbb... 2nd on b | |
744 | <aaaaaaa... 3rd on a | |
745 | <aaaaaaa... 2nd on a | |
746 | -yyyyyyy... 1st on b | |
747 | -xxxxxxx... 1st on a | |
748 | ----------------------------------------------------------------------- | |
749 | ||
750 | --graph:: | |
f98fd436 MG |
751 | Draw a text-based graphical representation of the commit history |
752 | on the left hand side of the output. This may cause extra lines | |
753 | to be printed in between commits, in order for the graph history | |
754 | to be drawn properly. | |
755 | + | |
756 | This enables parent rewriting, see 'History Simplification' below. | |
757 | + | |
4528aa1a JSJ |
758 | This implies the `--topo-order` option by default, but the |
759 | `--date-order` option may also be specified. | |
f98fd436 | 760 | |
1b32dece NTND |
761 | --show-linear-break[=<barrier>]:: |
762 | When --graph is not used, all history branches are flattened | |
763 | which can make it hard to see that the two consecutive commits | |
764 | do not belong to a linear branch. This option puts a barrier | |
765 | in between them in that case. If `<barrier>` is specified, it | |
766 | is the string that will be shown instead of the default one. | |
767 | ||
f98fd436 MG |
768 | ifdef::git-rev-list[] |
769 | --count:: | |
770 | Print a number stating how many commits would have been | |
771 | listed, and suppress all other output. When used together | |
4528aa1a | 772 | with `--left-right`, instead print the counts for left and |
b388e14b | 773 | right commits, separated by a tab. When used together with |
4528aa1a | 774 | `--cherry-mark`, omit patch equivalent commits from these |
b388e14b MG |
775 | counts and print the count for equivalent commits separated |
776 | by a tab. | |
f98fd436 MG |
777 | endif::git-rev-list[] |
778 | ||
f98fd436 MG |
779 | ifndef::git-rev-list[] |
780 | Diff Formatting | |
781 | ~~~~~~~~~~~~~~~ | |
782 | ||
19d6eb41 | 783 | Listed below are options that control the formatting of diff output. |
f98fd436 MG |
784 | Some of them are specific to linkgit:git-rev-list[1], however other diff |
785 | options may be given. See linkgit:git-diff-files[1] for more options. | |
786 | ||
787 | -c:: | |
f98fd436 MG |
788 | With this option, diff output for a merge commit |
789 | shows the differences from each of the parents to the merge result | |
790 | simultaneously instead of showing pairwise diff between a parent | |
791 | and the result one at a time. Furthermore, it lists only files | |
792 | which were modified from all parents. | |
793 | ||
794 | --cc:: | |
4528aa1a | 795 | This flag implies the `-c` option and further compresses the |
f98fd436 MG |
796 | patch output by omitting uninteresting hunks whose contents in |
797 | the parents have only two variants and the merge result picks | |
798 | one of them without modification. | |
799 | ||
800 | -m:: | |
f98fd436 MG |
801 | This flag makes the merge commits show the full diff like |
802 | regular commits; for each merge parent, a separate log entry | |
803 | and diff is generated. An exception is that only diff against | |
4528aa1a | 804 | the first parent is shown when `--first-parent` option is given; |
f98fd436 MG |
805 | in that case, the output represents the changes the merge |
806 | brought _into_ the then-current branch. | |
807 | ||
808 | -r:: | |
f98fd436 MG |
809 | Show recursive diffs. |
810 | ||
811 | -t:: | |
4528aa1a | 812 | Show the tree objects in the diff output. This implies `-r`. |
f98fd436 | 813 | endif::git-rev-list[] |