4 Besides specifying a range of commits that should be listed using the
5 special notations explained in the description, additional commit
6 limiting may be applied.
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.
13 Note that these are applied before commit
14 ordering and formatting options, such as `--reverse`.
18 --max-count=<number>::
19 Limit the number of commits to output.
22 Skip 'number' commits before starting to show the commit output.
26 Show commits more recent than a specific date.
30 Show commits older than a specific date.
33 --max-age=<timestamp>::
34 --min-age=<timestamp>::
35 Limit the commits output to specified time range.
39 --committer=<pattern>::
40 Limit the commits output to ones with author/committer
41 header lines that match the specified pattern (regular
42 expression). With more than one `--author=<pattern>`,
43 commits whose author matches any of the given patterns are
44 chosen (similarly for multiple `--committer=<pattern>`).
46 --grep-reflog=<pattern>::
47 Limit the commits output to ones with reflog entries that
48 match the specified pattern (regular expression). With
49 more than one `--grep-reflog`, commits whose reflog message
50 matches any of the given patterns are chosen. It is an
51 error to use this option unless `--walk-reflogs` is in use.
54 Limit the commits output to ones with log message that
55 matches the specified pattern (regular expression). With
56 more than one `--grep=<pattern>`, commits whose message
57 matches any of the given patterns are chosen (but see
59 ifndef::git-rev-list[]
61 When `--show-notes` is in effect, the message from the notes is
62 matched as if it were part of the log message.
66 Limit the commits output to ones that match all given `--grep`,
67 instead of ones that match at least one.
70 Limit the commits output to ones with log message that do not
71 match the pattern specified with `--grep=<pattern>`.
74 --regexp-ignore-case::
75 Match the regular expression limiting patterns without regard to letter
79 Consider the limiting patterns to be basic regular expressions;
84 Consider the limiting patterns to be extended regular expressions
85 instead of the default basic regular expressions.
89 Consider the limiting patterns to be fixed strings (don't interpret
90 pattern as a regular expression).
94 Consider the limiting patterns to be Perl-compatible regular
97 Support for these types of regular expressions is an optional
98 compile-time dependency. If Git wasn't compiled with support for them
99 providing this option will cause it to die.
102 Stop when a given path disappears from the tree.
105 Print only merge commits. This is exactly the same as `--min-parents=2`.
108 Do not print commits with more than one parent. This is
109 exactly the same as `--max-parents=1`.
111 --min-parents=<number>::
112 --max-parents=<number>::
115 Show only commits which have at least (or at most) that many parent
116 commits. In particular, `--max-parents=1` is the same as `--no-merges`,
117 `--min-parents=2` is the same as `--merges`. `--max-parents=0`
118 gives all root commits and `--min-parents=3` all octopus merges.
120 `--no-min-parents` and `--no-max-parents` reset these limits (to no limit)
121 again. Equivalent forms are `--min-parents=0` (any commit has 0 or more
122 parents) and `--max-parents=-1` (negative numbers denote no upper limit).
125 Follow only the first parent commit upon seeing a merge
126 commit. This option can give a better overview when
127 viewing the evolution of a particular topic branch,
128 because merges into a topic branch tend to be only about
129 adjusting to updated upstream from time to time, and
130 this option allows you to ignore the individual commits
131 brought in to your history by such a merge. Cannot be
132 combined with --bisect.
135 Reverses the meaning of the '{caret}' prefix (or lack thereof)
136 for all following revision specifiers, up to the next `--not`.
139 Pretend as if all the refs in `refs/`, along with `HEAD`, are
140 listed on the command line as '<commit>'.
142 --branches[=<pattern>]::
143 Pretend as if all the refs in `refs/heads` are listed
144 on the command line as '<commit>'. If '<pattern>' is given, limit
145 branches to ones matching given shell glob. If pattern lacks '?',
146 '{asterisk}', or '[', '/{asterisk}' at the end is implied.
149 Pretend as if all the refs in `refs/tags` are listed
150 on the command line as '<commit>'. If '<pattern>' is given, limit
151 tags to ones matching given shell glob. If pattern lacks '?', '{asterisk}',
152 or '[', '/{asterisk}' at the end is implied.
154 --remotes[=<pattern>]::
155 Pretend as if all the refs in `refs/remotes` are listed
156 on the command line as '<commit>'. If '<pattern>' is given, limit
157 remote-tracking branches to ones matching given shell glob.
158 If pattern lacks '?', '{asterisk}', or '[', '/{asterisk}' at the end is implied.
160 --glob=<glob-pattern>::
161 Pretend as if all the refs matching shell glob '<glob-pattern>'
162 are listed on the command line as '<commit>'. Leading 'refs/',
163 is automatically prepended if missing. If pattern lacks '?', '{asterisk}',
164 or '[', '/{asterisk}' at the end is implied.
166 --exclude=<glob-pattern>::
168 Do not include refs matching '<glob-pattern>' that the next `--all`,
169 `--branches`, `--tags`, `--remotes`, or `--glob` would otherwise
170 consider. Repetitions of this option accumulate exclusion patterns
171 up to the next `--all`, `--branches`, `--tags`, `--remotes`, or
172 `--glob` option (other options or arguments do not clear
173 accumulated patterns).
175 The patterns given should not begin with `refs/heads`, `refs/tags`, or
176 `refs/remotes` when applied to `--branches`, `--tags`, or `--remotes`,
177 respectively, and they must begin with `refs/` when applied to `--glob`
178 or `--all`. If a trailing '/{asterisk}' is intended, it must be given
182 Pretend as if all objects mentioned by reflogs are listed on the
183 command line as `<commit>`.
186 Pretend as if all objects mentioned as ref tips of alternate
187 repositories were listed on the command line. An alternate
188 repository is any repository whose object directory is specified
189 in `objects/info/alternates`. The set of included objects may
190 be modified by `core.alternateRefsCommand`, etc. See
191 linkgit:git-config[1].
194 By default, all working trees will be examined by the
195 following options when there are more than one (see
196 linkgit:git-worktree[1]): `--all`, `--reflog` and
198 This option forces them to examine the current working tree
202 Upon seeing an invalid object name in the input, pretend as if
203 the bad input was not given.
205 ifndef::git-rev-list[]
207 Pretend as if the bad bisection ref `refs/bisect/bad`
208 was listed and as if it was followed by `--not` and the good
209 bisection refs `refs/bisect/good-*` on the command
210 line. Cannot be combined with --first-parent.
211 endif::git-rev-list[]
214 In addition to the '<commit>' listed on the command
215 line, read them from the standard input. If a `--` separator is
216 seen, stop reading commits and start reading paths to limit the
219 ifdef::git-rev-list[]
221 Don't print anything to standard output. This form
222 is primarily meant to allow the caller to
223 test the exit status to see if a range of objects is fully
224 connected (or not). It is faster than redirecting stdout
225 to `/dev/null` as the output does not have to be formatted.
226 endif::git-rev-list[]
229 Like `--cherry-pick` (see below) but mark equivalent commits
230 with `=` rather than omitting them, and inequivalent ones with `+`.
233 Omit any commit that introduces the same change as
234 another commit on the ``other side'' when the set of
235 commits are limited with symmetric difference.
237 For example, if you have two branches, `A` and `B`, a usual way
238 to list all commits on only one side of them is with
239 `--left-right` (see the example below in the description of
240 the `--left-right` option). However, it shows the commits that were
241 cherry-picked from the other branch (for example, ``3rd on b'' may be
242 cherry-picked from branch A). With this option, such pairs of commits are
243 excluded from the output.
247 List only commits on the respective side of a symmetric difference,
248 i.e. only those which would be marked `<` resp. `>` by
251 For example, `--cherry-pick --right-only A...B` omits those
252 commits from `B` which are in `A` or are patch-equivalent to a commit in
253 `A`. In other words, this lists the `+` commits from `git cherry A B`.
254 More precisely, `--cherry-pick --right-only --no-merges` gives the exact
258 A synonym for `--right-only --cherry-mark --no-merges`; useful to
259 limit the output to the commits on our side and mark those that
260 have been applied to the other side of a forked history with
261 `git log --cherry upstream...mybranch`, similar to
262 `git cherry upstream mybranch`.
266 Instead of walking the commit ancestry chain, walk
267 reflog entries from the most recent one to older ones.
268 When this option is used you cannot specify commits to
269 exclude (that is, '{caret}commit', 'commit1..commit2',
270 and 'commit1\...commit2' notations cannot be used).
272 With `--pretty` format other than `oneline` and `reference` (for obvious reasons),
273 this causes the output to have two extra lines of information
274 taken from the reflog. The reflog designator in the output may be shown
275 as `ref@{Nth}` (where `Nth` is the reverse-chronological index in the
276 reflog) or as `ref@{timestamp}` (with the timestamp for that entry),
277 depending on a few rules:
280 1. If the starting point is specified as `ref@{Nth}`, show the index
283 2. If the starting point was specified as `ref@{now}`, show the
286 3. If neither was used, but `--date` was given on the command line, show
287 the timestamp in the format requested by `--date`.
289 4. Otherwise, show the index format.
292 Under `--pretty=oneline`, the commit message is
293 prefixed with this information on the same line.
294 This option cannot be combined with `--reverse`.
295 See also linkgit:git-reflog[1].
297 Under `--pretty=reference`, this information will not be shown at all.
300 After a failed merge, show refs that touch files having a
301 conflict and don't exist on all heads to merge.
304 Output excluded boundary commits. Boundary commits are
307 ifdef::git-rev-list[]
310 Try to speed up the traversal using the pack bitmap index (if
311 one is available). Note that when traversing with `--objects`,
312 trees and blobs will not have their associated path printed.
314 --progress=<header>::
315 Show progress reports on stderr as objects are considered. The
316 `<header>` text will be printed with each progress update.
317 endif::git-rev-list[]
319 History Simplification
320 ~~~~~~~~~~~~~~~~~~~~~~
322 Sometimes you are only interested in parts of the history, for example the
323 commits modifying a particular <path>. But there are two parts of
324 'History Simplification', one part is selecting the commits and the other
325 is how to do it, as there are various strategies to simplify the history.
327 The following options select the commits to be shown:
330 Commits modifying the given <paths> are selected.
332 --simplify-by-decoration::
333 Commits that are referred by some branch or tag are selected.
335 Note that extra commits can be shown to give a meaningful history.
337 The following options affect the way the simplification is performed:
340 Simplifies the history to the simplest history explaining the
341 final state of the tree. Simplest because it prunes some side
342 branches if the end result is the same (i.e. merging branches
343 with the same content)
346 Same as the default mode, but does not prune some history.
349 Only the selected commits are shown, plus some to have a
353 All commits in the simplified history are shown.
356 Additional option to `--full-history` to remove some needless
357 merges from the resulting history, as there are no selected
358 commits contributing to this merge.
361 When given a range of commits to display (e.g. 'commit1..commit2'
362 or 'commit2 {caret}commit1'), only display commits that exist
363 directly on the ancestry chain between the 'commit1' and
364 'commit2', i.e. commits that are both descendants of 'commit1',
365 and ancestors of 'commit2'.
367 A more detailed explanation follows.
369 Suppose you specified `foo` as the <paths>. We shall call commits
370 that modify `foo` !TREESAME, and the rest TREESAME. (In a diff
371 filtered for `foo`, they look different and equal, respectively.)
373 In the following, we will always refer to the same example history to
374 illustrate the differences between simplification settings. We assume
375 that you are filtering for a file `foo` in this commit graph:
376 -----------------------------------------------------------------------
377 .-A---M---N---O---P---Q
382 -----------------------------------------------------------------------
383 The horizontal line of history A---Q is taken to be the first parent of
384 each merge. The commits are:
386 * `I` is the initial commit, in which `foo` exists with contents
387 ``asdf'', and a file `quux` exists with contents ``quux''. Initial
388 commits are compared to an empty tree, so `I` is !TREESAME.
390 * In `A`, `foo` contains just ``foo''.
392 * `B` contains the same change as `A`. Its merge `M` is trivial and
393 hence TREESAME to all parents.
395 * `C` does not change `foo`, but its merge `N` changes it to ``foobar'',
396 so it is not TREESAME to any parent.
398 * `D` sets `foo` to ``baz''. Its merge `O` combines the strings from
399 `N` and `D` to ``foobarbaz''; i.e., it is not TREESAME to any parent.
401 * `E` changes `quux` to ``xyzzy'', and its merge `P` combines the
402 strings to ``quux xyzzy''. `P` is TREESAME to `O`, but not to `E`.
404 * `X` is an independent root commit that added a new file `side`, and `Y`
405 modified it. `Y` is TREESAME to `X`. Its merge `Q` added `side` to `P`, and
406 `Q` is TREESAME to `P`, but not to `Y`.
408 `rev-list` walks backwards through history, including or excluding
409 commits based on whether `--full-history` and/or parent rewriting
410 (via `--parents` or `--children`) are used. The following settings
414 Commits are included if they are not TREESAME to any parent
415 (though this can be changed, see `--sparse` below). If the
416 commit was a merge, and it was TREESAME to one parent, follow
417 only that parent. (Even if there are several TREESAME
418 parents, follow only one of them.) Otherwise, follow all
423 -----------------------------------------------------------------------
427 -----------------------------------------------------------------------
429 Note how the rule to only follow the TREESAME parent, if one is
430 available, removed `B` from consideration entirely. `C` was
431 considered via `N`, but is TREESAME. Root commits are compared to an
432 empty tree, so `I` is !TREESAME.
434 Parent/child relations are only visible with `--parents`, but that does
435 not affect the commits selected in default mode, so we have shown the
438 --full-history without parent rewriting::
439 This mode differs from the default in one point: always follow
440 all parents of a merge, even if it is TREESAME to one of them.
441 Even if more than one side of the merge has commits that are
442 included, this does not imply that the merge itself is! In
445 -----------------------------------------------------------------------
447 -----------------------------------------------------------------------
449 `M` was excluded because it is TREESAME to both parents. `E`,
450 `C` and `B` were all walked, but only `B` was !TREESAME, so the others
453 Note that without parent rewriting, it is not really possible to talk
454 about the parent/child relationships between the commits, so we show
457 --full-history with parent rewriting::
458 Ordinary commits are only included if they are !TREESAME
459 (though this can be changed, see `--sparse` below).
461 Merges are always included. However, their parent list is rewritten:
462 Along each parent, prune away commits that are not included
463 themselves. This results in
465 -----------------------------------------------------------------------
466 .-A---M---N---O---P---Q
471 -----------------------------------------------------------------------
473 Compare to `--full-history` without rewriting above. Note that `E`
474 was pruned away because it is TREESAME, but the parent list of P was
475 rewritten to contain `E`'s parent `I`. The same happened for `C` and
476 `N`, and `X`, `Y` and `Q`.
478 In addition to the above settings, you can change whether TREESAME
482 Commits that are walked are included if they are not TREESAME
486 All commits that are walked are included.
488 Note that without `--full-history`, this still simplifies merges: if
489 one of the parents is TREESAME, we follow only that one, so the other
490 sides of the merge are never walked.
493 First, build a history graph in the same way that
494 `--full-history` with parent rewriting does (see above).
496 Then simplify each commit `C` to its replacement `C'` in the final
497 history according to the following rules:
502 * Replace each parent `P` of `C'` with its simplification `P'`. In
503 the process, drop parents that are ancestors of other parents or that are
504 root commits TREESAME to an empty tree, and remove duplicates, but take care
505 to never drop all parents that we are TREESAME to.
507 * If after this parent rewriting, `C'` is a root or merge commit (has
508 zero or >1 parents), a boundary commit, or !TREESAME, it remains.
509 Otherwise, it is replaced with its only parent.
512 The effect of this is best shown by way of comparing to
513 `--full-history` with parent rewriting. The example turns into:
515 -----------------------------------------------------------------------
521 -----------------------------------------------------------------------
523 Note the major differences in `N`, `P`, and `Q` over `--full-history`:
526 * `N`'s parent list had `I` removed, because it is an ancestor of the
527 other parent `M`. Still, `N` remained because it is !TREESAME.
529 * `P`'s parent list similarly had `I` removed. `P` was then
530 removed completely, because it had one parent and is TREESAME.
532 * `Q`'s parent list had `Y` simplified to `X`. `X` was then removed, because it
533 was a TREESAME root. `Q` was then removed completely, because it had one
534 parent and is TREESAME.
537 Finally, there is a fifth simplification mode available:
540 Limit the displayed commits to those directly on the ancestry
541 chain between the ``from'' and ``to'' commits in the given commit
542 range. I.e. only display commits that are ancestor of the ``to''
543 commit and descendants of the ``from'' commit.
545 As an example use case, consider the following commit history:
547 -----------------------------------------------------------------------
550 B---C---G---H---I---J
552 A-------K---------------L--M
553 -----------------------------------------------------------------------
555 A regular 'D..M' computes the set of commits that are ancestors of `M`,
556 but excludes the ones that are ancestors of `D`. This is useful to see
557 what happened to the history leading to `M` since `D`, in the sense
558 that ``what does `M` have that did not exist in `D`''. The result in this
559 example would be all the commits, except `A` and `B` (and `D` itself,
562 When we want to find out what commits in `M` are contaminated with the
563 bug introduced by `D` and need fixing, however, we might want to view
564 only the subset of 'D..M' that are actually descendants of `D`, i.e.
565 excluding `C` and `K`. This is exactly what the `--ancestry-path`
566 option does. Applied to the 'D..M' range, it results in:
568 -----------------------------------------------------------------------
574 -----------------------------------------------------------------------
576 The `--simplify-by-decoration` option allows you to view only the
577 big picture of the topology of the history, by omitting commits
578 that are not referenced by tags. Commits are marked as !TREESAME
579 (in other words, kept after history simplification rules described
580 above) if (1) they are referenced by tags, or (2) they change the
581 contents of the paths given on the command line. All other
582 commits are marked as TREESAME (subject to be simplified away).
584 ifdef::git-rev-list[]
589 Limit output to the one commit object which is roughly halfway between
590 included and excluded commits. Note that the bad bisection ref
591 `refs/bisect/bad` is added to the included commits (if it
592 exists) and the good bisection refs `refs/bisect/good-*` are
593 added to the excluded commits (if they exist). Thus, supposing there
594 are no refs in `refs/bisect/`, if
596 -----------------------------------------------------------------------
597 $ git rev-list --bisect foo ^bar ^baz
598 -----------------------------------------------------------------------
600 outputs 'midpoint', the output of the two commands
602 -----------------------------------------------------------------------
603 $ git rev-list foo ^midpoint
604 $ git rev-list midpoint ^bar ^baz
605 -----------------------------------------------------------------------
607 would be of roughly the same length. Finding the change which
608 introduces a regression is thus reduced to a binary search: repeatedly
609 generate and test new 'midpoint's until the commit chain is of length
610 one. Cannot be combined with --first-parent.
613 This calculates the same as `--bisect`, except that refs in
614 `refs/bisect/` are not used, and except that this outputs
615 text ready to be eval'ed by the shell. These lines will assign the
616 name of the midpoint revision to the variable `bisect_rev`, and the
617 expected number of commits to be tested after `bisect_rev` is tested
618 to `bisect_nr`, the expected number of commits to be tested if
619 `bisect_rev` turns out to be good to `bisect_good`, the expected
620 number of commits to be tested if `bisect_rev` turns out to be bad to
621 `bisect_bad`, and the number of commits we are bisecting right now to
625 This outputs all the commit objects between the included and excluded
626 commits, ordered by their distance to the included and excluded
627 commits. Refs in `refs/bisect/` are not used. The farthest
628 from them is displayed first. (This is the only one displayed by
631 This is useful because it makes it easy to choose a good commit to
632 test when you want to avoid to test some of them for some reason (they
633 may not compile for example).
635 This option can be used along with `--bisect-vars`, in this case,
636 after all the sorted commit objects, there will be the same text as if
637 `--bisect-vars` had been used alone.
638 endif::git-rev-list[]
644 By default, the commits are shown in reverse chronological order.
647 Show no parents before all of its children are shown, but
648 otherwise show commits in the commit timestamp order.
650 --author-date-order::
651 Show no parents before all of its children are shown, but
652 otherwise show commits in the author timestamp order.
655 Show no parents before all of its children are shown, and
656 avoid showing commits on multiple lines of history
659 For example, in a commit history like this:
661 ----------------------------------------------------------------
667 ----------------------------------------------------------------
669 where the numbers denote the order of commit timestamps, `git
670 rev-list` and friends with `--date-order` show the commits in the
671 timestamp order: 8 7 6 5 4 3 2 1.
673 With `--topo-order`, they would show 8 6 5 3 7 4 2 1 (or 8 7 4 2 6 5
674 3 1); some older commits are shown before newer ones in order to
675 avoid showing the commits from two parallel development track mixed
679 Output the commits chosen to be shown (see Commit Limiting
680 section above) in reverse order. Cannot be combined with
686 These options are mostly targeted for packing of Git repositories.
688 ifdef::git-rev-list[]
690 Print the object IDs of any object referenced by the listed
691 commits. `--objects foo ^bar` thus means ``send me
692 all object IDs which I need to download if I have the commit
693 object _bar_ but not _foo_''.
696 Print tree and blob ids in order of the commits. The tree
697 and blob ids are printed after they are first referenced
701 Similar to `--objects`, but also print the IDs of excluded
702 commits prefixed with a ``-'' character. This is used by
703 linkgit:git-pack-objects[1] to build a ``thin'' pack, which records
704 objects in deltified form based on objects contained in these
705 excluded commits to reduce network traffic.
707 --objects-edge-aggressive::
708 Similar to `--objects-edge`, but it tries harder to find excluded
709 commits at the cost of increased time. This is used instead of
710 `--objects-edge` to build ``thin'' packs for shallow repositories.
713 Pretend as if all trees and blobs used by the index are listed
714 on the command line. Note that you probably want to use
718 Only useful with `--objects`; print the object IDs that are not
722 Only useful with `--objects`; print the names of the object IDs
723 that are found. This is the default behavior.
726 Only useful with `--objects`; does not print the names of the object
727 IDs that are found. This inverts `--object-names`. This flag allows
728 the output to be more easily parsed by commands such as
729 linkgit:git-cat-file[1].
731 --filter=<filter-spec>::
732 Only useful with one of the `--objects*`; omits objects (usually
733 blobs) from the list of printed objects. The '<filter-spec>'
734 may be one of the following:
736 The form '--filter=blob:none' omits all blobs.
738 The form '--filter=blob:limit=<n>[kmg]' omits blobs larger than n bytes
739 or units. n may be zero. The suffixes k, m, and g can be used to name
740 units in KiB, MiB, or GiB. For example, 'blob:limit=1k' is the same
741 as 'blob:limit=1024'.
743 The form '--filter=sparse:oid=<blob-ish>' uses a sparse-checkout
744 specification contained in the blob (or blob-expression) '<blob-ish>'
745 to omit blobs that would not be not required for a sparse checkout on
748 The form '--filter=tree:<depth>' omits all blobs and trees whose depth
749 from the root tree is >= <depth> (minimum depth if an object is located
750 at multiple depths in the commits traversed). <depth>=0 will not include
751 any trees or blobs unless included explicitly in the command-line (or
752 standard input when --stdin is used). <depth>=1 will include only the
753 tree and blobs which are referenced directly by a commit reachable from
754 <commit> or an explicitly-given object. <depth>=2 is like <depth>=1
755 while also including trees and blobs one more level removed from an
756 explicitly-given commit or tree.
758 Note that the form '--filter=sparse:path=<path>' that wants to read
759 from an arbitrary path on the filesystem has been dropped for security
763 Turn off any previous `--filter=` argument.
765 --filter-print-omitted::
766 Only useful with `--filter=`; prints a list of the objects omitted
767 by the filter. Object IDs are prefixed with a ``~'' character.
769 --missing=<missing-action>::
770 A debug option to help with future "partial clone" development.
771 This option specifies how missing objects are handled.
773 The form '--missing=error' requests that rev-list stop with an error if
774 a missing object is encountered. This is the default action.
776 The form '--missing=allow-any' will allow object traversal to continue
777 if a missing object is encountered. Missing objects will silently be
778 omitted from the results.
780 The form '--missing=allow-promisor' is like 'allow-any', but will only
781 allow object traversal to continue for EXPECTED promisor missing objects.
782 Unexpected missing objects will raise an error.
784 The form '--missing=print' is like 'allow-any', but will also print a
785 list of the missing objects. Object IDs are prefixed with a ``?'' character.
787 --exclude-promisor-objects::
788 (For internal use only.) Prefilter object traversal at
789 promisor boundary. This is used with partial clone. This is
790 stronger than `--missing=allow-promisor` because it limits the
791 traversal, rather than just silencing errors about missing
793 endif::git-rev-list[]
795 --no-walk[=(sorted|unsorted)]::
796 Only show the given commits, but do not traverse their ancestors.
797 This has no effect if a range is specified. If the argument
798 `unsorted` is given, the commits are shown in the order they were
799 given on the command line. Otherwise (if `sorted` or no argument
800 was given), the commits are shown in reverse chronological order
802 Cannot be combined with `--graph`.
805 Overrides a previous `--no-walk`.
810 ifdef::git-rev-list[]
811 Using these options, linkgit:git-rev-list[1] will act similar to the
812 more specialized family of commit log tools: linkgit:git-log[1],
813 linkgit:git-show[1], and linkgit:git-whatchanged[1]
814 endif::git-rev-list[]
816 include::pretty-options.txt[]
819 Synonym for `--date=relative`.
822 Only takes effect for dates shown in human-readable format, such
823 as when using `--pretty`. `log.date` config variable sets a default
824 value for the log command's `--date` option. By default, dates
825 are shown in the original time zone (either committer's or
826 author's). If `-local` is appended to the format (e.g.,
827 `iso-local`), the user's local time zone is used instead.
830 `--date=relative` shows dates relative to the current time,
831 e.g. ``2 hours ago''. The `-local` option has no effect for
834 `--date=local` is an alias for `--date=default-local`.
836 `--date=iso` (or `--date=iso8601`) shows timestamps in a ISO 8601-like format.
837 The differences to the strict ISO 8601 format are:
839 - a space instead of the `T` date/time delimiter
840 - a space between time and time zone
841 - no colon between hours and minutes of the time zone
843 `--date=iso-strict` (or `--date=iso8601-strict`) shows timestamps in strict
846 `--date=rfc` (or `--date=rfc2822`) shows timestamps in RFC 2822
847 format, often found in email messages.
849 `--date=short` shows only the date, but not the time, in `YYYY-MM-DD` format.
851 `--date=raw` shows the date as seconds since the epoch (1970-01-01
852 00:00:00 UTC), followed by a space, and then the timezone as an offset
853 from UTC (a `+` or `-` with four digits; the first two are hours, and
854 the second two are minutes). I.e., as if the timestamp were formatted
855 with `strftime("%s %z")`).
856 Note that the `-local` option does not affect the seconds-since-epoch
857 value (which is always measured in UTC), but does switch the accompanying
860 `--date=human` shows the timezone if the timezone does not match the
861 current time-zone, and doesn't print the whole date if that matches
862 (ie skip printing year for dates that are "this year", but also skip
863 the whole date itself if it's in the last few days and we can just say
864 what weekday it was). For older dates the hour and minute is also
867 `--date=unix` shows the date as a Unix epoch timestamp (seconds since
868 1970). As with `--raw`, this is always in UTC and therefore `-local`
871 `--date=format:...` feeds the format `...` to your system `strftime`,
872 except for %z and %Z, which are handled internally.
873 Use `--date=format:%c` to show the date in your system locale's
874 preferred format. See the `strftime` manual for a complete list of
875 format placeholders. When using `-local`, the correct syntax is
876 `--date=format-local:...`.
878 `--date=default` is the default format, and is similar to
879 `--date=rfc2822`, with a few exceptions:
881 - there is no comma after the day-of-week
883 - the time zone is omitted when the local time zone is used
885 ifdef::git-rev-list[]
887 Print the contents of the commit in raw-format; each record is
888 separated with a NUL character.
889 endif::git-rev-list[]
892 Print also the parents of the commit (in the form "commit parent...").
893 Also enables parent rewriting, see 'History Simplification' above.
896 Print also the children of the commit (in the form "commit child...").
897 Also enables parent rewriting, see 'History Simplification' above.
899 ifdef::git-rev-list[]
901 Print the raw commit timestamp.
902 endif::git-rev-list[]
905 Mark which side of a symmetric difference a commit is reachable from.
906 Commits from the left side are prefixed with `<` and those from
907 the right with `>`. If combined with `--boundary`, those
908 commits are prefixed with `-`.
910 For example, if you have this topology:
912 -----------------------------------------------------------------------
917 o---x---a---a branch A
918 -----------------------------------------------------------------------
920 you would get an output like this:
922 -----------------------------------------------------------------------
923 $ git rev-list --left-right --boundary --pretty=oneline A...B
931 -----------------------------------------------------------------------
934 Draw a text-based graphical representation of the commit history
935 on the left hand side of the output. This may cause extra lines
936 to be printed in between commits, in order for the graph history
937 to be drawn properly.
938 Cannot be combined with `--no-walk`.
940 This enables parent rewriting, see 'History Simplification' above.
942 This implies the `--topo-order` option by default, but the
943 `--date-order` option may also be specified.
945 --show-linear-break[=<barrier>]::
946 When --graph is not used, all history branches are flattened
947 which can make it hard to see that the two consecutive commits
948 do not belong to a linear branch. This option puts a barrier
949 in between them in that case. If `<barrier>` is specified, it
950 is the string that will be shown instead of the default one.
952 ifdef::git-rev-list[]
954 Print a number stating how many commits would have been
955 listed, and suppress all other output. When used together
956 with `--left-right`, instead print the counts for left and
957 right commits, separated by a tab. When used together with
958 `--cherry-mark`, omit patch equivalent commits from these
959 counts and print the count for equivalent commits separated
961 endif::git-rev-list[]
963 ifndef::git-rev-list[]
967 Listed below are options that control the formatting of diff output.
968 Some of them are specific to linkgit:git-rev-list[1], however other diff
969 options may be given. See linkgit:git-diff-files[1] for more options.
972 With this option, diff output for a merge commit
973 shows the differences from each of the parents to the merge result
974 simultaneously instead of showing pairwise diff between a parent
975 and the result one at a time. Furthermore, it lists only files
976 which were modified from all parents.
979 This flag implies the `-c` option and further compresses the
980 patch output by omitting uninteresting hunks whose contents in
981 the parents have only two variants and the merge result picks
982 one of them without modification.
984 --combined-all-paths::
985 This flag causes combined diffs (used for merge commits) to
986 list the name of the file from all parents. It thus only has
987 effect when -c or --cc are specified, and is likely only
988 useful if filename changes are detected (i.e. when either
989 rename or copy detection have been requested).
992 This flag makes the merge commits show the full diff like
993 regular commits; for each merge parent, a separate log entry
994 and diff is generated. An exception is that only diff against
995 the first parent is shown when `--first-parent` option is given;
996 in that case, the output represents the changes the merge
997 brought _into_ the then-current branch.
1000 Show recursive diffs.
1003 Show the tree objects in the diff output. This implies `-r`.
1004 endif::git-rev-list[]