5 Using these options, linkgit:git-rev-list[1] will act similar to the
6 more specialized family of commit log tools: linkgit:git-log[1],
7 linkgit:git-show[1], and linkgit:git-whatchanged[1]
10 include::pretty-options.txt[]
14 Synonym for `--date=relative`.
16 --date={relative,local,default,iso,rfc}::
18 Only takes effect for dates shown in human-readable format, such
19 as when using "--pretty".
21 `--date=relative` shows dates relative to the current time,
24 `--date=local` shows timestamps in user's local timezone.
26 `--date=iso` (or `--date=iso8601`) shows timestamps in ISO 8601 format.
28 `--date=rfc` (or `--date=rfc2822`) shows timestamps in RFC 2822
29 format, often found in E-mail messages.
31 `--date=short` shows only date but not time, in `YYYY-MM-DD` format.
33 `--date=default` shows timestamps in the original timezone
34 (either committer's or author's).
38 Print the contents of the commit in raw-format; each record is
39 separated with a NUL character.
43 Print the parents of the commit.
46 Print the raw commit timestamp.
50 Mark which side of a symmetric diff a commit is reachable from.
51 Commits from the left side are prefixed with `<` and those from
52 the right with `>`. If combined with `--boundary`, those
53 commits are prefixed with `-`.
55 For example, if you have this topology:
57 -----------------------------------------------------------------------
62 o---x---a---a branch A
63 -----------------------------------------------------------------------
65 you would get an output line this:
67 -----------------------------------------------------------------------
68 $ git rev-list --left-right --boundary --pretty=oneline A...B
76 -----------------------------------------------------------------------
80 Draw a text-based graphical representation of the commit history
81 on the left hand side of the output. This may cause extra lines
82 to be printed in between commits, in order for the graph history
85 This implies the '--topo-order' option by default, but the
86 '--date-order' option may also be specified.
91 Below are listed options that control the formatting of diff output.
92 Some of them are specific to linkgit:git-rev-list[1], however other diff
93 options may be given. See linkgit:git-diff-files[1] for more options.
97 This flag changes the way a merge commit is displayed. It shows
98 the differences from each of the parents to the merge result
99 simultaneously instead of showing pairwise diff between a parent
100 and the result one at a time. Furthermore, it lists only files
101 which were modified from all parents.
105 This flag implies the '-c' options and further compresses the
106 patch output by omitting hunks that show differences from only
107 one parent, or show the same change from all but one parent for
112 Show recursive diffs.
116 Show the tree objects in the diff output. This implies '-r'.
121 Besides specifying a range of commits that should be listed using the
122 special notations explained in the description, additional commit
123 limiting may be applied.
127 -n 'number', --max-count='number'::
129 Limit the number of commits output.
133 Skip 'number' commits before starting to show the commit output.
135 --since='date', --after='date'::
137 Show commits more recent than a specific date.
139 --until='date', --before='date'::
141 Show commits older than a specific date.
143 ifdef::git-rev-list[]
144 --max-age='timestamp', --min-age='timestamp'::
146 Limit the commits output to specified time range.
147 endif::git-rev-list[]
149 --author='pattern', --committer='pattern'::
151 Limit the commits output to ones with author/committer
152 header lines that match the specified pattern (regular expression).
156 Limit the commits output to ones with log message that
157 matches the specified pattern (regular expression).
159 -i, --regexp-ignore-case::
161 Match the regexp limiting patterns without regard to letters case.
163 -E, --extended-regexp::
165 Consider the limiting patterns to be extended regular expressions
166 instead of the default basic regular expressions.
168 -F, --fixed-strings::
170 Consider the limiting patterns to be fixed strings (don't interpret
171 pattern as a regular expression).
175 Stop when a given path disappears from the tree.
179 Show also parts of history irrelevant to current state of a given
180 path. This turns off history simplification, which removed merges
181 which didn't change anything at all at some child. It will still actually
182 simplify away merges that didn't change anything at all into either
187 Do not print commits with more than one parent.
190 Follow only the first parent commit upon seeing a merge
191 commit. This option can give a better overview when
192 viewing the evolution of a particular topic branch,
193 because merges into a topic branch tend to be only about
194 adjusting to updated upstream from time to time, and
195 this option allows you to ignore the individual commits
196 brought in to your history by such a merge.
200 Reverses the meaning of the '{caret}' prefix (or lack thereof)
201 for all following revision specifiers, up to the next '--not'.
205 Pretend as if all the refs in `$GIT_DIR/refs/` are listed on the
206 command line as '<commit>'.
210 In addition to the '<commit>' listed on the command
211 line, read them from the standard input.
215 Don't print anything to standard output. This form
216 is primarily meant to allow the caller to
217 test the exit status to see if a range of objects is fully
218 connected (or not). It is faster than redirecting stdout
219 to /dev/null as the output does not have to be formatted.
223 Omit any commit that introduces the same change as
224 another commit on the "other side" when the set of
225 commits are limited with symmetric difference.
227 For example, if you have two branches, `A` and `B`, a usual way
228 to list all commits on only one side of them is with
229 `--left-right`, like the example above in the description of
230 that option. It however shows the commits that were cherry-picked
231 from the other branch (for example, "3rd on b" may be cherry-picked
232 from branch A). With this option, such pairs of commits are
233 excluded from the output.
237 Instead of walking the commit ancestry chain, walk
238 reflog entries from the most recent one to older ones.
239 When this option is used you cannot specify commits to
240 exclude (that is, '{caret}commit', 'commit1..commit2',
241 nor 'commit1...commit2' notations cannot be used).
243 With '\--pretty' format other than oneline (for obvious reasons),
244 this causes the output to have two extra lines of information
245 taken from the reflog. By default, 'commit@\{Nth}' notation is
246 used in the output. When the starting commit is specified as
247 'commit@{now}', output also uses 'commit@\{timestamp}' notation
248 instead. Under '\--pretty=oneline', the commit message is
249 prefixed with this information on the same line.
251 Cannot be combined with '\--reverse'.
252 See also linkgit:git-reflog[1].
256 After a failed merge, show refs that touch files having a
257 conflict and don't exist on all heads to merge.
261 Output uninteresting commits at the boundary, which are usually
266 When optional paths are given, the default behaviour ('--dense') is to
267 only output commits that changes at least one of them, and also ignore
268 merges that do not touch the given paths.
270 Use the '--sparse' flag to makes the command output all eligible commits
271 (still subject to count and age limitation), but apply merge
272 simplification nevertheless.
274 ifdef::git-rev-list[]
277 Limit output to the one commit object which is roughly halfway between
278 the included and excluded commits. Thus, if
280 -----------------------------------------------------------------------
281 $ git-rev-list --bisect foo ^bar ^baz
282 -----------------------------------------------------------------------
284 outputs 'midpoint', the output of the two commands
286 -----------------------------------------------------------------------
287 $ git-rev-list foo ^midpoint
288 $ git-rev-list midpoint ^bar ^baz
289 -----------------------------------------------------------------------
291 would be of roughly the same length. Finding the change which
292 introduces a regression is thus reduced to a binary search: repeatedly
293 generate and test new 'midpoint's until the commit chain is of length
298 This calculates the same as `--bisect`, but outputs text ready
299 to be eval'ed by the shell. These lines will assign the name of
300 the midpoint revision to the variable `bisect_rev`, and the
301 expected number of commits to be tested after `bisect_rev` is
302 tested to `bisect_nr`, the expected number of commits to be
303 tested if `bisect_rev` turns out to be good to `bisect_good`,
304 the expected number of commits to be tested if `bisect_rev`
305 turns out to be bad to `bisect_bad`, and the number of commits
306 we are bisecting right now to `bisect_all`.
310 This outputs all the commit objects between the included and excluded
311 commits, ordered by their distance to the included and excluded
312 commits. The farthest from them is displayed first. (This is the only
313 one displayed by `--bisect`.)
315 This is useful because it makes it easy to choose a good commit to
316 test when you want to avoid to test some of them for some reason (they
317 may not compile for example).
319 This option can be used along with `--bisect-vars`, in this case,
320 after all the sorted commit objects, there will be the same text as if
321 `--bisect-vars` had been used alone.
322 endif::git-rev-list[]
329 By default, the commits are shown in reverse chronological order.
333 This option makes them appear in topological order (i.e.
334 descendant commits are shown before their parents).
338 This option is similar to '--topo-order' in the sense that no
339 parent comes before all of its children, but otherwise things
340 are still ordered in the commit timestamp order.
344 Output the commits in reverse order.
345 Cannot be combined with '\--walk-reflogs'.
350 These options are mostly targeted for packing of git repositories.
354 Print the object IDs of any object referenced by the listed
355 commits. '--objects foo ^bar' thus means "send me
356 all object IDs which I need to download if I have the commit
357 object 'bar', but not 'foo'".
361 Similar to '--objects', but also print the IDs of excluded
362 commits prefixed with a "-" character. This is used by
363 linkgit:git-pack-objects[1] to build "thin" pack, which records
364 objects in deltified form based on objects contained in these
365 excluded commits to reduce network traffic.
369 Only useful with '--objects'; print the object IDs that are not
374 Only show the given revs, but do not traverse their ancestors.
378 Overrides a previous --no-walk.