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 -----------------------------------------------------------------------
81 Below are listed options that control the formatting of diff output.
82 Some of them are specific to linkgit:git-rev-list[1], however other diff
83 options may be given. See linkgit:git-diff-files[1] for more options.
87 This flag changes the way a merge commit is displayed. It shows
88 the differences from each of the parents to the merge result
89 simultaneously instead of showing pairwise diff between a parent
90 and the result one at a time. Furthermore, it lists only files
91 which were modified from all parents.
95 This flag implies the '-c' options and further compresses the
96 patch output by omitting hunks that show differences from only
97 one parent, or show the same change from all but one parent for
102 Show recursive diffs.
106 Show the tree objects in the diff output. This implies '-r'.
111 Besides specifying a range of commits that should be listed using the
112 special notations explained in the description, additional commit
113 limiting may be applied.
117 -n 'number', --max-count='number'::
119 Limit the number of commits output.
123 Skip 'number' commits before starting to show the commit output.
125 --since='date', --after='date'::
127 Show commits more recent than a specific date.
129 --until='date', --before='date'::
131 Show commits older than a specific date.
133 --max-age='timestamp', --min-age='timestamp'::
135 Limit the commits output to specified time range.
137 --author='pattern', --committer='pattern'::
139 Limit the commits output to ones with author/committer
140 header lines that match the specified pattern (regular expression).
144 Limit the commits output to ones with log message that
145 matches the specified pattern (regular expression).
147 -i, --regexp-ignore-case::
149 Match the regexp limiting patterns without regard to letters case.
151 -E, --extended-regexp::
153 Consider the limiting patterns to be extended regular expressions
154 instead of the default basic regular expressions.
156 -F, --fixed-strings::
158 Consider the limiting patterns to be fixed strings (don't interpret
159 pattern as a regular expression).
163 Stop when a given path disappears from the tree.
167 Show also parts of history irrelevant to current state of a given
168 path. This turns off history simplification, which removed merges
169 which didn't change anything at all at some child. It will still actually
170 simplify away merges that didn't change anything at all into either
175 Do not print commits with more than one parent.
178 Follow only the first parent commit upon seeing a merge
179 commit. This option can give a better overview when
180 viewing the evolution of a particular topic branch,
181 because merges into a topic branch tend to be only about
182 adjusting to updated upstream from time to time, and
183 this option allows you to ignore the individual commits
184 brought in to your history by such a merge.
188 Reverses the meaning of the '{caret}' prefix (or lack thereof)
189 for all following revision specifiers, up to the next '--not'.
193 Pretend as if all the refs in `$GIT_DIR/refs/` are listed on the
194 command line as '<commit>'.
198 In addition to the '<commit>' listed on the command
199 line, read them from the standard input.
203 Don't print anything to standard output. This form
204 is primarily meant to allow the caller to
205 test the exit status to see if a range of objects is fully
206 connected (or not). It is faster than redirecting stdout
207 to /dev/null as the output does not have to be formatted.
211 Omit any commit that introduces the same change as
212 another commit on the "other side" when the set of
213 commits are limited with symmetric difference.
215 For example, if you have two branches, `A` and `B`, a usual way
216 to list all commits on only one side of them is with
217 `--left-right`, like the example above in the description of
218 that option. It however shows the commits that were cherry-picked
219 from the other branch (for example, "3rd on b" may be cherry-picked
220 from branch A). With this option, such pairs of commits are
221 excluded from the output.
225 Instead of walking the commit ancestry chain, walk
226 reflog entries from the most recent one to older ones.
227 When this option is used you cannot specify commits to
228 exclude (that is, '{caret}commit', 'commit1..commit2',
229 nor 'commit1...commit2' notations cannot be used).
231 With '\--pretty' format other than oneline (for obvious reasons),
232 this causes the output to have two extra lines of information
233 taken from the reflog. By default, 'commit@\{Nth}' notation is
234 used in the output. When the starting commit is specified as
235 'commit@{now}', output also uses 'commit@\{timestamp}' notation
236 instead. Under '\--pretty=oneline', the commit message is
237 prefixed with this information on the same line.
239 Cannot be combined with '\--reverse'.
240 See also linkgit:git-reflog[1].
244 After a failed merge, show refs that touch files having a
245 conflict and don't exist on all heads to merge.
249 Output uninteresting commits at the boundary, which are usually
254 When optional paths are given, the default behaviour ('--dense') is to
255 only output commits that changes at least one of them, and also ignore
256 merges that do not touch the given paths.
258 Use the '--sparse' flag to makes the command output all eligible commits
259 (still subject to count and age limitation), but apply merge
260 simplification nevertheless.
262 ifdef::git-rev-list[]
265 Limit output to the one commit object which is roughly halfway between
266 the included and excluded commits. Thus, if
268 -----------------------------------------------------------------------
269 $ git-rev-list --bisect foo ^bar ^baz
270 -----------------------------------------------------------------------
272 outputs 'midpoint', the output of the two commands
274 -----------------------------------------------------------------------
275 $ git-rev-list foo ^midpoint
276 $ git-rev-list midpoint ^bar ^baz
277 -----------------------------------------------------------------------
279 would be of roughly the same length. Finding the change which
280 introduces a regression is thus reduced to a binary search: repeatedly
281 generate and test new 'midpoint's until the commit chain is of length
286 This calculates the same as `--bisect`, but outputs text ready
287 to be eval'ed by the shell. These lines will assign the name of
288 the midpoint revision to the variable `bisect_rev`, and the
289 expected number of commits to be tested after `bisect_rev` is
290 tested to `bisect_nr`, the expected number of commits to be
291 tested if `bisect_rev` turns out to be good to `bisect_good`,
292 the expected number of commits to be tested if `bisect_rev`
293 turns out to be bad to `bisect_bad`, and the number of commits
294 we are bisecting right now to `bisect_all`.
298 This outputs all the commit objects between the included and excluded
299 commits, ordered by their distance to the included and excluded
300 commits. The farthest from them is displayed first. (This is the only
301 one displayed by `--bisect`.)
303 This is useful because it makes it easy to choose a good commit to
304 test when you want to avoid to test some of them for some reason (they
305 may not compile for example).
307 This option can be used along with `--bisect-vars`, in this case,
308 after all the sorted commit objects, there will be the same text as if
309 `--bisect-vars` had been used alone.
310 endif::git-rev-list[]
317 By default, the commits are shown in reverse chronological order.
321 This option makes them appear in topological order (i.e.
322 descendant commits are shown before their parents).
326 This option is similar to '--topo-order' in the sense that no
327 parent comes before all of its children, but otherwise things
328 are still ordered in the commit timestamp order.
332 Output the commits in reverse order.
333 Cannot be combined with '\--walk-reflogs'.
338 These options are mostly targeted for packing of git repositories.
342 Print the object IDs of any object referenced by the listed
343 commits. '--objects foo ^bar' thus means "send me
344 all object IDs which I need to download if I have the commit
345 object 'bar', but not 'foo'".
349 Similar to '--objects', but also print the IDs of excluded
350 commits prefixed with a "-" character. This is used by
351 linkgit:git-pack-objects[1] to build "thin" pack, which records
352 objects in deltified form based on objects contained in these
353 excluded commits to reduce network traffic.
357 Only useful with '--objects'; print the object IDs that are not
362 Only show the given revs, but do not traverse their ancestors.
366 Overrides a previous --no-walk.