1 .\"Generated by db2man.xsl. Don't modify this, modify the source.
10 .de Sp \" Vertical space (when we can't use .PP)
16 .ie \\n(.$>=3 .ne \\$3
20 .TH "GIT-REV-LIST" 1 "" "" ""
22 git-rev-list \- Lists commit objects in reverse chronological order
26 git\-rev\-list [ \-\-max\-count=number ] [ \-\-max\-age=timestamp ] [ \-\-min\-age=timestamp ] [ \-\-sparse ] [ \-\-no\-merges ] [ \-\-all ] [ [ \-\-merge\-order [ \-\-show\-breaks ] ] | [ \-\-topo\-order ] | ] [ \-\-parents ] [ \-\-objects [ \-\-unpacked ] ] [ \-\-pretty | \-\-header | ] [ \-\-bisect ] <commit>... [ \-\- <paths>... ]
31 Lists commit objects in reverse chronological order starting at the given commit(s), taking ancestry relationship into account\&. This is useful to produce human\-readable log output\&.
34 Commits which are stated with a preceding ^ cause listing to stop at that point\&. Their parents are implied\&. "git\-rev\-list foo bar ^baz" thus means "list all the commits which are included in foo and bar, but not in baz"\&.
37 A special notation <commit1>\&.\&.<commit2> can be used as a short\-hand for ^<commit1> <commit2>\&.
43 Print the contents of the commit changesets in human\-readable form\&.
47 Print the contents of the commit in raw\-format; each record is separated with a NUL character\&.
51 Print the object IDs of any object referenced by the listed commits\&. git\-rev\-list \-\-objects foo ^bar thus means "send me all object IDs which I need to download if I have the commit object bar, but not foo"\&.
55 Only useful with \-\-objects; print the object IDs that are not in packs\&.
59 Limit output to the one commit object which is roughly halfway between the included and excluded commits\&. Thus, if git\-rev\-list \-\-bisect foo bar baz outputs midpoint, the output of git\-rev\-list foo ^midpoint and git\-rev\-list midpoint bar baz would be of roughly the same length\&. Finding the change which introduces a regression is thus reduced to a binary search: repeatedly generate and test new 'midpoint's until the commit chain is of length one\&.
63 Limit the number of commits output\&.
66 \-\-max\-age=timestamp, \-\-min\-age=timestamp
67 Limit the commits output to specified time range\&.
71 When optional paths are given, the command outputs only the commits that changes at least one of them, and also ignores merges that do not touch the given paths\&. This flag makes the command output all eligible commits (still subject to count and age limitation), but apply merge simplification nevertheless\&.
75 Pretend as if all the refs in $GIT_DIR/refs/ are listed on the command line as <commit>\&.
79 By default, the commits are shown in reverse chronological order\&. This option makes them appear in topological order (i\&.e\&. descendant commits are shown before their parents)\&.
83 When specified the commit history is decomposed into a unique sequence of minimal, non\-linear epochs and maximal, linear epochs\&. Non\-linear epochs are then linearised by sorting them into merge order, which is described below\&.
85 Maximal, linear epochs correspond to periods of sequential development\&. Minimal, non\-linear epochs correspond to periods of divergent development followed by a converging merge\&. The theory of epochs is described in more detail at http://blackcubes\&.dyndns\&.org/epoch/: \fIhttp://blackcubes.dyndns.org/epoch/\fR\&.
87 The merge order for a non\-linear epoch is defined as a linearisation for which the following invariants are true:
92 if a commit P is reachable from commit N, commit P sorts after commit N in the linearised list\&.
95 if Pi and Pj are any two parents of a merge M (with i < j), then any commit N, such that N is reachable from Pj but not reachable from Pi, sorts before all commits reachable from Pi\&.
97 Invariant 1 states that later commits appear before earlier commits they are derived from\&.
99 Invariant 2 states that commits unique to "later" parents in a merge, appear before all commits from "earlier" parents of a merge\&.
106 Each item of the list is output with a 2\-character prefix consisting of one of: (|), (^), (=) followed by a space\&.
108 Commits marked with (=) represent the boundaries of minimal, non\-linear epochs and correspond either to the start of a period of divergent development or to the end of such a period\&.
110 Commits marked with (|) are direct parents of commits immediately preceding the marked commit in the list\&.
112 Commits marked with (^) are not parents of the immediately preceding commit\&. These "breaks" represent necessary discontinuities implied by trying to represent an arbtirary DAG in a linear form\&.
114 \-\-show\-breaks is only valid if \-\-merge\-order is also specified\&.
119 Written by Linus Torvalds <torvalds@osdl\&.org>
122 Original \-\-merge\-order logic by Jon Seymour <jon\&.seymour@gmail\&.com>
127 Documentation by David Greaves, Junio C Hamano and the git\-list <git@vger\&.kernel\&.org>\&.
132 Part of the \fBgit\fR(7) suite