command to control what is shown and how, and options applicable to\r
the <a href="git-diff-tree.html">git-diff-tree(1)</a> commands to control how the changes\r
each commit introduces are shown.</p>\r
-<p>This manual page describes only the most frequently used options.</p>\r
</div>\r
<h2>OPTIONS</h2>\r
<div class="sectionbody">\r
<dl>\r
<dt>\r
---pretty[=<em><format></em>]\r
-</dt>\r
-<dd>\r
-<p>\r
- Pretty-print the contents of the commit logs in a given format,\r
- where <em><format></em> can be one of <em>oneline</em>, <em>short</em>, <em>medium</em>,\r
- <em>full</em>, <em>fuller</em>, <em>email</em>, <em>raw</em> and <em>format:<string></em>.\r
- When omitted, the format defaults to <em>medium</em>.\r
-</p>\r
-</dd>\r
-<dt>\r
---abbrev-commit\r
-</dt>\r
-<dd>\r
-<p>\r
- Instead of showing the full 40-byte hexadecimal commit object\r
- name, show only handful hexdigits prefix. Non default number of\r
- digits can be specified with "--abbrev=<n>" (which also modifies\r
- diff output, if it is displayed).\r
-</p>\r
-<p>This should make "--pretty=oneline" a whole lot more readable for\r
-people using 80-column terminals.</p>\r
-</dd>\r
-<dt>\r
---encoding[=<encoding>]\r
-</dt>\r
-<dd>\r
-<p>\r
- The commit objects record the encoding used for the log message\r
- in their encoding header; this option can be used to tell the\r
- command to re-code the commit log message in the encoding\r
- preferred by the user. For non plumbing commands this\r
- defaults to UTF-8.\r
-</p>\r
-</dd>\r
-</dl>\r
-<dl>\r
-<dt>\r
-p\r
</dt>\r
<dd>\r
</p>\r
</dd>\r
<dt>\r
+--decorate\r
+</dt>\r
+<dd>\r
+<p>\r
+ Print out the ref names of any commits that are shown.\r
+</p>\r
+</dd>\r
+<dt>\r
+--full-diff\r
+</dt>\r
+<dd>\r
+<p>\r
+ Without this flag, "git log -p <paths>…" shows commits that\r
+ touch the specified paths, and diffs about the same specified\r
+ paths. With this, the full diff is shown for commits that touch\r
+ the specified paths; this means that "<paths>…" limits only\r
+ commits, and doesn't limit diff for those commits.\r
+</p>\r
+</dd>\r
+<dt>\r
+--follow\r
+</dt>\r
+<dd>\r
+<p>\r
+ Continue listing the history of a file beyond renames.\r
+</p>\r
+</dd>\r
+<dt>\r
+--log-size\r
+</dt>\r
+<dd>\r
+<p>\r
+ Before the log message print out its size in bytes. Intended\r
+ mainly for porcelain tools consumption. If git is unable to\r
+ produce a valid value size is set to zero.\r
+ Note that only message is considered, if also a diff is shown\r
+ its size is not included.\r
+</p>\r
+</dd>\r
+<dt>\r
+<paths>…\r
+</dt>\r
+<dd>\r
+<p>\r
+ Show only commits that affect the specified paths.\r
+</p>\r
+</dd>\r
+</dl>\r
+<h3>Commit Formatting</h3>\r
+<dl>\r
+<dt>\r
+--pretty[=<em><format></em>]\r
+</dt>\r
+<dd>\r
+<p>\r
+ Pretty-print the contents of the commit logs in a given format,\r
+ where <em><format></em> can be one of <em>oneline</em>, <em>short</em>, <em>medium</em>,\r
+ <em>full</em>, <em>fuller</em>, <em>email</em>, <em>raw</em> and <em>format:<string></em>.\r
+ When omitted, the format defaults to <em>medium</em>.\r
+</p>\r
+</dd>\r
+<dt>\r
+--abbrev-commit\r
+</dt>\r
+<dd>\r
+<p>\r
+ Instead of showing the full 40-byte hexadecimal commit object\r
+ name, show only handful hexdigits prefix. Non default number of\r
+ digits can be specified with "--abbrev=<n>" (which also modifies\r
+ diff output, if it is displayed).\r
+</p>\r
+<p>This should make "--pretty=oneline" a whole lot more readable for\r
+people using 80-column terminals.</p>\r
+</dd>\r
+<dt>\r
+--encoding[=<encoding>]\r
+</dt>\r
+<dd>\r
+<p>\r
+ The commit objects record the encoding used for the log message\r
+ in their encoding header; this option can be used to tell the\r
+ command to re-code the commit log message in the encoding\r
+ preferred by the user. For non plumbing commands this\r
+ defaults to UTF-8.\r
+</p>\r
+</dd>\r
+<dt>\r
+--relative-date\r
+</dt>\r
+<dd>\r
+<p>\r
+ Synonym for <tt>--date=relative</tt>.\r
+</p>\r
+</dd>\r
+<dt>\r
+--date={relative,local,default,iso,rfc}\r
+</dt>\r
+<dd>\r
+<p>\r
+ Only takes effect for dates shown in human-readable format, such\r
+ as when using "--pretty".\r
+</p>\r
+<p><tt>--date=relative</tt> shows dates relative to the current time,\r
+e.g. "2 hours ago".</p>\r
+<p><tt>--date=local</tt> shows timestamps in user's local timezone.</p>\r
+<p><tt>--date=iso</tt> (or <tt>--date=iso8601</tt>) shows timestamps in ISO 8601 format.</p>\r
+<p><tt>--date=rfc</tt> (or <tt>--date=rfc2822</tt>) shows timestamps in RFC 2822\r
+format, often found in E-mail messages.</p>\r
+<p><tt>--date=short</tt> shows only date but not time, in <tt>YYYY-MM-DD</tt> format.</p>\r
+<p><tt>--date=default</tt> shows timestamps in the original timezone\r
+(either committer's or author's).</p>\r
+</dd>\r
+<dt>\r
+--header\r
+</dt>\r
+<dd>\r
+<p>\r
+ Print the contents of the commit in raw-format; each record is\r
+ separated with a NUL character.\r
+</p>\r
+</dd>\r
+<dt>\r
+--parents\r
+</dt>\r
+<dd>\r
+<p>\r
+ Print the parents of the commit.\r
+</p>\r
+</dd>\r
+<dt>\r
+--timestamp\r
+</dt>\r
+<dd>\r
+<p>\r
+ Print the raw commit timestamp.\r
+</p>\r
+</dd>\r
+<dt>\r
+--left-right\r
+</dt>\r
+<dd>\r
+<p>\r
+ Mark which side of a symmetric diff a commit is reachable from.\r
+ Commits from the left side are prefixed with <tt><</tt> and those from\r
+ the right with <tt>></tt>. If combined with <tt>--boundary</tt>, those\r
+ commits are prefixed with <tt>-</tt>.\r
+</p>\r
+<p>For example, if you have this topology:</p>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt> y---b---b branch B\r
+ / \ /\r
+ / .\r
+ / / \\r
+ o---x---a---a branch A</tt></pre>\r
+</div></div>\r
+<p>you would get an output line this:</p>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt> $ git rev-list --left-right --boundary --pretty=oneline A...B\r
+\r
+ >bbbbbbb... 3rd on b\r
+ >bbbbbbb... 2nd on b\r
+ <aaaaaaa... 3rd on a\r
+ <aaaaaaa... 2nd on a\r
+ -yyyyyyy... 1st on b\r
+ -xxxxxxx... 1st on a</tt></pre>\r
+</div></div>\r
+</dd>\r
+</dl>\r
+<h3>Diff Formatting</h3>\r
+<p>Below are listed options that control the formatting of diff output.\r
+Some of them are specific to <a href="git-rev-list.html">git-rev-list(1)</a>, however other diff\r
+options may be given. See <a href="git-diff-files.html">git-diff-files(1)</a> for more options.</p>\r
+<dl>\r
+<dt>\r
+-c\r
+</dt>\r
+<dd>\r
+<p>\r
+ This flag changes the way a merge commit is displayed. It shows\r
+ the differences from each of the parents to the merge result\r
+ simultaneously instead of showing pairwise diff between a parent\r
+ and the result one at a time. Furthermore, it lists only files\r
+ which were modified from all parents.\r
+</p>\r
+</dd>\r
+<dt>\r
+--cc\r
+</dt>\r
+<dd>\r
+<p>\r
+ This flag implies the <em>-c</em> options and further compresses the\r
+ patch output by omitting hunks that show differences from only\r
+ one parent, or show the same change from all but one parent for\r
+ an Octopus merge.\r
+</p>\r
+</dd>\r
+<dt>\r
+-r\r
+</dt>\r
+<dd>\r
+<p>\r
+ Show recursive diffs.\r
+</p>\r
+</dd>\r
+<dt>\r
+-t\r
+</dt>\r
+<dd>\r
+<p>\r
+ Show the tree objects in the diff output. This implies <em>-r</em>.\r
+</p>\r
+</dd>\r
+</dl>\r
+<h3>Commit Limiting</h3>\r
+<p>Besides specifying a range of commits that should be listed using the\r
+special notations explained in the description, additional commit\r
+limiting may be applied.</p>\r
+<dl>\r
+<dt>\r
+-n <em>number</em>, --max-count=<em>number</em>\r
+</dt>\r
+<dd>\r
+<p>\r
+ Limit the number of commits output.\r
+</p>\r
+</dd>\r
+<dt>\r
+--skip=<em>number</em>\r
+</dt>\r
+<dd>\r
+<p>\r
+ Skip <em>number</em> commits before starting to show the commit output.\r
+</p>\r
+</dd>\r
+<dt>\r
+--since=<em>date</em>, --after=<em>date</em>\r
+</dt>\r
+<dd>\r
+<p>\r
+ Show commits more recent than a specific date.\r
+</p>\r
+</dd>\r
+<dt>\r
+--until=<em>date</em>, --before=<em>date</em>\r
+</dt>\r
+<dd>\r
+<p>\r
+ Show commits older than a specific date.\r
+</p>\r
+</dd>\r
+<dt>\r
+--max-age=<em>timestamp</em>, --min-age=<em>timestamp</em>\r
+</dt>\r
+<dd>\r
+<p>\r
+ Limit the commits output to specified time range.\r
+</p>\r
+</dd>\r
+<dt>\r
+--author=<em>pattern</em>, --committer=<em>pattern</em>\r
+</dt>\r
+<dd>\r
+<p>\r
+ Limit the commits output to ones with author/committer\r
+ header lines that match the specified pattern (regular expression).\r
+</p>\r
+</dd>\r
+<dt>\r
+--grep=<em>pattern</em>\r
+</dt>\r
+<dd>\r
+<p>\r
+ Limit the commits output to ones with log message that\r
+ matches the specified pattern (regular expression).\r
+</p>\r
+</dd>\r
+<dt>\r
+-i, --regexp-ignore-case\r
+</dt>\r
+<dd>\r
+<p>\r
+ Match the regexp limiting patterns without regard to letters case.\r
+</p>\r
+</dd>\r
+<dt>\r
+-E, --extended-regexp\r
+</dt>\r
+<dd>\r
+<p>\r
+ Consider the limiting patterns to be extended regular expressions\r
+ instead of the default basic regular expressions.\r
+</p>\r
+</dd>\r
+<dt>\r
+--remove-empty\r
+</dt>\r
+<dd>\r
+<p>\r
+ Stop when a given path disappears from the tree.\r
+</p>\r
+</dd>\r
+<dt>\r
+--full-history\r
+</dt>\r
+<dd>\r
+<p>\r
+ Show also parts of history irrelevant to current state of a given\r
+ path. This turns off history simplification, which removed merges\r
+ which didn't change anything at all at some child. It will still actually\r
+ simplify away merges that didn't change anything at all into either\r
+ child.\r
+</p>\r
+</dd>\r
+<dt>\r
+--no-merges\r
+</dt>\r
+<dd>\r
+<p>\r
+ Do not print commits with more than one parent.\r
+</p>\r
+</dd>\r
+<dt>\r
--first-parent\r
</dt>\r
<dd>\r
</p>\r
</dd>\r
<dt>\r
+--not\r
+</dt>\r
+<dd>\r
+<p>\r
+ Reverses the meaning of the <em>^</em> prefix (or lack thereof)\r
+ for all following revision specifiers, up to the next <em>--not</em>.\r
+</p>\r
+</dd>\r
+<dt>\r
+--all\r
+</dt>\r
+<dd>\r
+<p>\r
+ Pretend as if all the refs in <tt>$GIT_DIR/refs/</tt> are listed on the\r
+ command line as <em><commit></em>.\r
+</p>\r
+</dd>\r
+<dt>\r
+--stdin\r
+</dt>\r
+<dd>\r
+<p>\r
+ In addition to the <em><commit></em> listed on the command\r
+ line, read them from the standard input.\r
+</p>\r
+</dd>\r
+<dt>\r
+--quiet\r
+</dt>\r
+<dd>\r
+<p>\r
+ Don't print anything to standard output. This form\r
+ is primarily meant to allow the caller to\r
+ test the exit status to see if a range of objects is fully\r
+ connected (or not). It is faster than redirecting stdout\r
+ to /dev/null as the output does not have to be formatted.\r
+</p>\r
+</dd>\r
+<dt>\r
+--cherry-pick\r
+</dt>\r
+<dd>\r
+<p>\r
+ Omit any commit that introduces the same change as\r
+ another commit on the "other side" when the set of\r
+ commits are limited with symmetric difference.<br />\r
+For example, if you have two branches, <tt>A</tt> and <tt>B</tt>, a usual way\r
+to list all commits on only one side of them is with\r
+<tt>--left-right</tt>, like the example above in the description of\r
+that option. It however shows the commits that were cherry-picked\r
+from the other branch (for example, "3rd on b" may be cherry-picked\r
+from branch A). With this option, such pairs of commits are\r
+excluded from the output.\r
+</p>\r
+</dd>\r
+<dt>\r
-g, --walk-reflogs\r
</dt>\r
<dd>\r
<p>\r
- Show commits as they were recorded in the reflog. The log contains\r
- a record about how the tip of a reference was changed.\r
- Cannot be combined with --reverse.\r
- See also <a href="git-reflog.html">git-reflog(1)</a>.\r
+ Instead of walking the commit ancestry chain, walk\r
+ reflog entries from the most recent one to older ones.\r
+ When this option is used you cannot specify commits to\r
+ exclude (that is, <em>^commit</em>, <em>commit1..commit2</em>,\r
+ nor <em>commit1…commit2</em> notations cannot be used).<br />\r
+With <em>--pretty</em> format other than oneline (for obvious reasons),\r
+this causes the output to have two extra lines of information\r
+taken from the reflog. By default, <em>commit@{Nth}</em> notation is\r
+used in the output. When the starting commit is specified as\r
+instead. Under <em>--pretty=oneline</em>, the commit message is\r
+prefixed with this information on the same line.\r
</p>\r
+<p>Cannot be combined with <em>--reverse</em>.\r
+See also <a href="git-reflog.html">git-reflog(1)</a>.</p>\r
</dd>\r
<dt>\r
---decorate\r
+--merge\r
</dt>\r
<dd>\r
<p>\r
- Print out the ref names of any commits that are shown.\r
+ After a failed merge, show refs that touch files having a\r
+ conflict and don't exist on all heads to merge.\r
</p>\r
</dd>\r
<dt>\r
---full-diff\r
+--boundary\r
</dt>\r
<dd>\r
<p>\r
- Without this flag, "git log -p <paths>…" shows commits that\r
- touch the specified paths, and diffs about the same specified\r
- paths. With this, the full diff is shown for commits that touch\r
- the specified paths; this means that "<paths>…" limits only\r
- commits, and doesn't limit diff for those commits.\r
+ Output uninteresting commits at the boundary, which are usually\r
+ not shown.\r
</p>\r
</dd>\r
<dt>\r
---follow\r
+--dense, --sparse\r
</dt>\r
<dd>\r
<p>\r
- Continue listing the history of a file beyond renames.\r
+When optional paths are given, the default behaviour (<em>--dense</em>) is to\r
+only output commits that changes at least one of them, and also ignore\r
+merges that do not touch the given paths.\r
</p>\r
+<p>Use the <em>--sparse</em> flag to makes the command output all eligible commits\r
+(still subject to count and age limitation), but apply merge\r
+simplification nevertheless.</p>\r
</dd>\r
+</dl>\r
+<h3>Commit Ordering</h3>\r
+<p>By default, the commits are shown in reverse chronological order.</p>\r
+<dl>\r
<dt>\r
---log-size\r
+--topo-order\r
</dt>\r
<dd>\r
<p>\r
- Before the log message print out its size in bytes. Intended\r
- mainly for porcelain tools consumption. If git is unable to\r
- produce a valid value size is set to zero.\r
- Note that only message is considered, if also a diff is shown\r
- its size is not included.\r
+ This option makes them appear in topological order (i.e.\r
+ descendant commits are shown before their parents).\r
</p>\r
</dd>\r
<dt>\r
-<paths>…\r
+--date-order\r
</dt>\r
<dd>\r
<p>\r
- Show only commits that affect the specified paths.\r
+ This option is similar to <em>--topo-order</em> in the sense that no\r
+ parent comes before all of its children, but otherwise things\r
+ are still ordered in the commit timestamp order.\r
+</p>\r
+</dd>\r
+<dt>\r
+--reverse\r
+</dt>\r
+<dd>\r
+<p>\r
+ Output the commits in reverse order.\r
+ Cannot be combined with <em>--walk-reflogs</em>.\r
+</p>\r
+</dd>\r
+</dl>\r
+<h3>Object Traversal</h3>\r
+<p>These options are mostly targeted for packing of git repositories.</p>\r
+<dl>\r
+<dt>\r
+--objects\r
+</dt>\r
+<dd>\r
+<p>\r
+ Print the object IDs of any object referenced by the listed\r
+ commits. <em>--objects foo ^bar</em> thus means "send me\r
+ all object IDs which I need to download if I have the commit\r
+ object <em>bar</em>, but not <em>foo</em>".\r
+</p>\r
+</dd>\r
+<dt>\r
+--objects-edge\r
+</dt>\r
+<dd>\r
+<p>\r
+ Similar to <em>--objects</em>, but also print the IDs of excluded\r
+ commits prefixed with a "-" character. This is used by\r
+ <a href="git-pack-objects.html">git-pack-objects(1)</a> to build "thin" pack, which records\r
+ objects in deltified form based on objects contained in these\r
+ excluded commits to reduce network traffic.\r
+</p>\r
+</dd>\r
+<dt>\r
+--unpacked\r
+</dt>\r
+<dd>\r
+<p>\r
+ Only useful with <em>--objects</em>; print the object IDs that are not\r
+ in packs.\r
+</p>\r
+</dd>\r
+<dt>\r
+--no-walk\r
+</dt>\r
+<dd>\r
+<p>\r
+ Only show the given revs, but do not traverse their ancestors.\r
+</p>\r
+</dd>\r
+<dt>\r
+--do-walk\r
+</dt>\r
+<dd>\r
+<p>\r
+ Overrides a previous --no-walk.\r
</p>\r
</dd>\r
</dl>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 07-Jan-2008 07:50:27 UTC\r
+Last updated 19-Jan-2008 08:01:34 UTC\r
</div>\r
</div>\r
</body>\r
the linkgit:git-diff-tree[1] commands to control how the changes
each commit introduces are shown.
-This manual page describes only the most frequently used options.
-
OPTIONS
-------
-include::pretty-options.txt[]
-
:git-log: 1
include::diff-options.txt[]
and <until>, see "SPECIFYING REVISIONS" section in
linkgit:git-rev-parse[1].
---first-parent::
- Follow only the first parent commit upon seeing a merge
- commit. This option can give a better overview when
- viewing the evolution of a particular topic branch,
- because merges into a topic branch tend to be only about
- adjusting to updated upstream from time to time, and
- this option allows you to ignore the individual commits
- brought in to your history by such a merge.
-
--g, \--walk-reflogs::
- Show commits as they were recorded in the reflog. The log contains
- a record about how the tip of a reference was changed.
- Cannot be combined with --reverse.
- See also linkgit:git-reflog[1].
-
--decorate::
Print out the ref names of any commits that are shown.
Show only commits that affect the specified paths.
+include::rev-list-options.txt[]
+
include::pretty-formats.txt[]
include::diff-generate-patch.txt[]
</dt>\r
<dd>\r
<p>\r
- Don't print anything to standard output. This form of\r
- git-rev-list is primarily meant to allow the caller to\r
+ Don't print anything to standard output. This form\r
+ is primarily meant to allow the caller to\r
test the exit status to see if a range of objects is fully\r
connected (or not). It is faster than redirecting stdout\r
to /dev/null as the output does not have to be formatted.\r
instead. Under <em>--pretty=oneline</em>, the commit message is\r
prefixed with this information on the same line.\r
</p>\r
-<p>Cannot be combined with <em>--reverse</em>.</p>\r
+<p>Cannot be combined with <em>--reverse</em>.\r
+See also <a href="git-reflog.html">git-reflog(1)</a>.</p>\r
</dd>\r
<dt>\r
--merge\r
<dd>\r
<p>\r
Print the object IDs of any object referenced by the listed\r
- commits. <em>git-rev-list --objects foo ^bar</em> thus means "send me\r
+ commits. <em>--objects foo ^bar</em> thus means "send me\r
all object IDs which I need to download if I have the commit\r
object <em>bar</em>, but not <em>foo</em>".\r
</p>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 07-Jan-2008 07:50:44 UTC\r
+Last updated 19-Jan-2008 08:01:34 UTC\r
</div>\r
</div>\r
</body>\r
OPTIONS
-------
-Commit Formatting
-~~~~~~~~~~~~~~~~~
-
-Using these options, linkgit:git-rev-list[1] will act similar to the
-more specialized family of commit log tools: linkgit:git-log[1],
-linkgit:git-show[1], and linkgit:git-whatchanged[1]
-
-include::pretty-options.txt[]
-
---relative-date::
-
- Synonym for `--date=relative`.
-
---date={relative,local,default,iso,rfc}::
-
- Only takes effect for dates shown in human-readable format, such
- as when using "--pretty".
-+
-`--date=relative` shows dates relative to the current time,
-e.g. "2 hours ago".
-+
-`--date=local` shows timestamps in user's local timezone.
-+
-`--date=iso` (or `--date=iso8601`) shows timestamps in ISO 8601 format.
-+
-`--date=rfc` (or `--date=rfc2822`) shows timestamps in RFC 2822
-format, often found in E-mail messages.
-+
-`--date=short` shows only date but not time, in `YYYY-MM-DD` format.
-+
-`--date=default` shows timestamps in the original timezone
-(either committer's or author's).
-
---header::
-
- Print the contents of the commit in raw-format; each record is
- separated with a NUL character.
-
---parents::
-
- Print the parents of the commit.
-
---timestamp::
- Print the raw commit timestamp.
-
---left-right::
-
- Mark which side of a symmetric diff a commit is reachable from.
- Commits from the left side are prefixed with `<` and those from
- the right with `>`. If combined with `--boundary`, those
- commits are prefixed with `-`.
-+
-For example, if you have this topology:
-+
------------------------------------------------------------------------
- y---b---b branch B
- / \ /
- / .
- / / \
- o---x---a---a branch A
------------------------------------------------------------------------
-+
-you would get an output line this:
-+
------------------------------------------------------------------------
- $ git rev-list --left-right --boundary --pretty=oneline A...B
-
- >bbbbbbb... 3rd on b
- >bbbbbbb... 2nd on b
- <aaaaaaa... 3rd on a
- <aaaaaaa... 2nd on a
- -yyyyyyy... 1st on b
- -xxxxxxx... 1st on a
------------------------------------------------------------------------
-
-Diff Formatting
-~~~~~~~~~~~~~~~
-
-Below are listed options that control the formatting of diff output.
-Some of them are specific to linkgit:git-rev-list[1], however other diff
-options may be given. See linkgit:git-diff-files[1] for more options.
-
--c::
-
- This flag changes the way a merge commit is displayed. It shows
- the differences from each of the parents to the merge result
- simultaneously instead of showing pairwise diff between a parent
- and the result one at a time. Furthermore, it lists only files
- which were modified from all parents.
-
---cc::
-
- This flag implies the '-c' options and further compresses the
- patch output by omitting hunks that show differences from only
- one parent, or show the same change from all but one parent for
- an Octopus merge.
-
--r::
-
- Show recursive diffs.
-
--t::
-
- Show the tree objects in the diff output. This implies '-r'.
-
-Commit Limiting
-~~~~~~~~~~~~~~~
-
-Besides specifying a range of commits that should be listed using the
-special notations explained in the description, additional commit
-limiting may be applied.
-
---
-
--n 'number', --max-count='number'::
-
- Limit the number of commits output.
-
---skip='number'::
-
- Skip 'number' commits before starting to show the commit output.
-
---since='date', --after='date'::
-
- Show commits more recent than a specific date.
-
---until='date', --before='date'::
-
- Show commits older than a specific date.
-
---max-age='timestamp', --min-age='timestamp'::
-
- Limit the commits output to specified time range.
-
---author='pattern', --committer='pattern'::
-
- Limit the commits output to ones with author/committer
- header lines that match the specified pattern (regular expression).
-
---grep='pattern'::
-
- Limit the commits output to ones with log message that
- matches the specified pattern (regular expression).
-
--i, --regexp-ignore-case::
-
- Match the regexp limiting patterns without regard to letters case.
-
--E, --extended-regexp::
-
- Consider the limiting patterns to be extended regular expressions
- instead of the default basic regular expressions.
-
---remove-empty::
-
- Stop when a given path disappears from the tree.
-
---full-history::
-
- Show also parts of history irrelevant to current state of a given
- path. This turns off history simplification, which removed merges
- which didn't change anything at all at some child. It will still actually
- simplify away merges that didn't change anything at all into either
- child.
-
---no-merges::
-
- Do not print commits with more than one parent.
-
---first-parent::
- Follow only the first parent commit upon seeing a merge
- commit. This option can give a better overview when
- viewing the evolution of a particular topic branch,
- because merges into a topic branch tend to be only about
- adjusting to updated upstream from time to time, and
- this option allows you to ignore the individual commits
- brought in to your history by such a merge.
-
---not::
-
- Reverses the meaning of the '{caret}' prefix (or lack thereof)
- for all following revision specifiers, up to the next '--not'.
-
---all::
-
- Pretend as if all the refs in `$GIT_DIR/refs/` are listed on the
- command line as '<commit>'.
-
---stdin::
-
- In addition to the '<commit>' listed on the command
- line, read them from the standard input.
-
---quiet::
-
- Don't print anything to standard output. This form of
- git-rev-list is primarily meant to allow the caller to
- test the exit status to see if a range of objects is fully
- connected (or not). It is faster than redirecting stdout
- to /dev/null as the output does not have to be formatted.
-
---cherry-pick::
-
- Omit any commit that introduces the same change as
- another commit on the "other side" when the set of
- commits are limited with symmetric difference.
-+
-For example, if you have two branches, `A` and `B`, a usual way
-to list all commits on only one side of them is with
-`--left-right`, like the example above in the description of
-that option. It however shows the commits that were cherry-picked
-from the other branch (for example, "3rd on b" may be cherry-picked
-from branch A). With this option, such pairs of commits are
-excluded from the output.
-
--g, --walk-reflogs::
-
- Instead of walking the commit ancestry chain, walk
- reflog entries from the most recent one to older ones.
- When this option is used you cannot specify commits to
- exclude (that is, '{caret}commit', 'commit1..commit2',
- nor 'commit1...commit2' notations cannot be used).
-+
-With '\--pretty' format other than oneline (for obvious reasons),
-this causes the output to have two extra lines of information
-taken from the reflog. By default, 'commit@\{Nth}' notation is
-used in the output. When the starting commit is specified as
-'commit@{now}', output also uses 'commit@\{timestamp}' notation
-instead. Under '\--pretty=oneline', the commit message is
-prefixed with this information on the same line.
-
-Cannot be combined with '\--reverse'.
-
---merge::
-
- After a failed merge, show refs that touch files having a
- conflict and don't exist on all heads to merge.
-
---boundary::
-
- Output uninteresting commits at the boundary, which are usually
- not shown.
-
---dense, --sparse::
-
-When optional paths are given, the default behaviour ('--dense') is to
-only output commits that changes at least one of them, and also ignore
-merges that do not touch the given paths.
-
-Use the '--sparse' flag to makes the command output all eligible commits
-(still subject to count and age limitation), but apply merge
-simplification nevertheless.
-
---bisect::
-
-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 the two commands
-
------------------------------------------------------------------------
- $ git-rev-list foo ^midpoint
- $ 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.
-
---bisect-vars::
-
-This calculates the same as `--bisect`, but outputs text ready
-to be eval'ed by the shell. These lines will assign the name of
-the midpoint revision to the variable `bisect_rev`, and the
-expected number of commits to be tested after `bisect_rev` is
-tested to `bisect_nr`, the expected number of commits to be
-tested if `bisect_rev` turns out to be good to `bisect_good`,
-the expected number of commits to be tested if `bisect_rev`
-turns out to be bad to `bisect_bad`, and the number of commits
-we are bisecting right now to `bisect_all`.
-
---bisect-all::
-
-This outputs all the commit objects between the included and excluded
-commits, ordered by their distance to the included and excluded
-commits. The farthest from them is displayed first. (This is the only
-one displayed by `--bisect`.)
-
-This is useful because it makes it easy to choose a good commit to
-test when you want to avoid to test some of them for some reason (they
-may not compile for example).
-
-This option can be used along with `--bisect-vars`, in this case,
-after all the sorted commit objects, there will be the same text as if
-`--bisect-vars` had been used alone.
-
---
-
-Commit Ordering
-~~~~~~~~~~~~~~~
-
-By default, the commits are shown in reverse chronological order.
-
---topo-order::
-
- This option makes them appear in topological order (i.e.
- descendant commits are shown before their parents).
-
---date-order::
-
- This option is similar to '--topo-order' in the sense that no
- parent comes before all of its children, but otherwise things
- are still ordered in the commit timestamp order.
-
---reverse::
-
- Output the commits in reverse order.
- Cannot be combined with '\--walk-reflogs'.
-
-Object Traversal
-~~~~~~~~~~~~~~~~
-
-These options are mostly targeted for packing of git repositories.
-
---objects::
-
- 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'".
-
---objects-edge::
-
- Similar to '--objects', but also print the IDs of excluded
- commits prefixed with a "-" character. This is used by
- linkgit:git-pack-objects[1] to build "thin" pack, which records
- objects in deltified form based on objects contained in these
- excluded commits to reduce network traffic.
-
---unpacked::
-
- Only useful with '--objects'; print the object IDs that are not
- in packs.
-
---no-walk::
-
- Only show the given revs, but do not traverse their ancestors.
-
---do-walk::
-
- Overrides a previous --no-walk.
-
+:git-rev-list: 1
+include::rev-list-options.txt[]
include::pretty-formats.txt[]
--- /dev/null
+Commit Formatting
+~~~~~~~~~~~~~~~~~
+
+ifdef::git-rev-list[]
+Using these options, linkgit:git-rev-list[1] will act similar to the
+more specialized family of commit log tools: linkgit:git-log[1],
+linkgit:git-show[1], and linkgit:git-whatchanged[1]
+endif::git-rev-list[]
+
+include::pretty-options.txt[]
+
+--relative-date::
+
+ Synonym for `--date=relative`.
+
+--date={relative,local,default,iso,rfc}::
+
+ Only takes effect for dates shown in human-readable format, such
+ as when using "--pretty".
++
+`--date=relative` shows dates relative to the current time,
+e.g. "2 hours ago".
++
+`--date=local` shows timestamps in user's local timezone.
++
+`--date=iso` (or `--date=iso8601`) shows timestamps in ISO 8601 format.
++
+`--date=rfc` (or `--date=rfc2822`) shows timestamps in RFC 2822
+format, often found in E-mail messages.
++
+`--date=short` shows only date but not time, in `YYYY-MM-DD` format.
++
+`--date=default` shows timestamps in the original timezone
+(either committer's or author's).
+
+--header::
+
+ Print the contents of the commit in raw-format; each record is
+ separated with a NUL character.
+
+--parents::
+
+ Print the parents of the commit.
+
+--timestamp::
+ Print the raw commit timestamp.
+
+--left-right::
+
+ Mark which side of a symmetric diff a commit is reachable from.
+ Commits from the left side are prefixed with `<` and those from
+ the right with `>`. If combined with `--boundary`, those
+ commits are prefixed with `-`.
++
+For example, if you have this topology:
++
+-----------------------------------------------------------------------
+ y---b---b branch B
+ / \ /
+ / .
+ / / \
+ o---x---a---a branch A
+-----------------------------------------------------------------------
++
+you would get an output line this:
++
+-----------------------------------------------------------------------
+ $ git rev-list --left-right --boundary --pretty=oneline A...B
+
+ >bbbbbbb... 3rd on b
+ >bbbbbbb... 2nd on b
+ <aaaaaaa... 3rd on a
+ <aaaaaaa... 2nd on a
+ -yyyyyyy... 1st on b
+ -xxxxxxx... 1st on a
+-----------------------------------------------------------------------
+
+Diff Formatting
+~~~~~~~~~~~~~~~
+
+Below are listed options that control the formatting of diff output.
+Some of them are specific to linkgit:git-rev-list[1], however other diff
+options may be given. See linkgit:git-diff-files[1] for more options.
+
+-c::
+
+ This flag changes the way a merge commit is displayed. It shows
+ the differences from each of the parents to the merge result
+ simultaneously instead of showing pairwise diff between a parent
+ and the result one at a time. Furthermore, it lists only files
+ which were modified from all parents.
+
+--cc::
+
+ This flag implies the '-c' options and further compresses the
+ patch output by omitting hunks that show differences from only
+ one parent, or show the same change from all but one parent for
+ an Octopus merge.
+
+-r::
+
+ Show recursive diffs.
+
+-t::
+
+ Show the tree objects in the diff output. This implies '-r'.
+
+Commit Limiting
+~~~~~~~~~~~~~~~
+
+Besides specifying a range of commits that should be listed using the
+special notations explained in the description, additional commit
+limiting may be applied.
+
+--
+
+-n 'number', --max-count='number'::
+
+ Limit the number of commits output.
+
+--skip='number'::
+
+ Skip 'number' commits before starting to show the commit output.
+
+--since='date', --after='date'::
+
+ Show commits more recent than a specific date.
+
+--until='date', --before='date'::
+
+ Show commits older than a specific date.
+
+--max-age='timestamp', --min-age='timestamp'::
+
+ Limit the commits output to specified time range.
+
+--author='pattern', --committer='pattern'::
+
+ Limit the commits output to ones with author/committer
+ header lines that match the specified pattern (regular expression).
+
+--grep='pattern'::
+
+ Limit the commits output to ones with log message that
+ matches the specified pattern (regular expression).
+
+-i, --regexp-ignore-case::
+
+ Match the regexp limiting patterns without regard to letters case.
+
+-E, --extended-regexp::
+
+ Consider the limiting patterns to be extended regular expressions
+ instead of the default basic regular expressions.
+
+--remove-empty::
+
+ Stop when a given path disappears from the tree.
+
+--full-history::
+
+ Show also parts of history irrelevant to current state of a given
+ path. This turns off history simplification, which removed merges
+ which didn't change anything at all at some child. It will still actually
+ simplify away merges that didn't change anything at all into either
+ child.
+
+--no-merges::
+
+ Do not print commits with more than one parent.
+
+--first-parent::
+ Follow only the first parent commit upon seeing a merge
+ commit. This option can give a better overview when
+ viewing the evolution of a particular topic branch,
+ because merges into a topic branch tend to be only about
+ adjusting to updated upstream from time to time, and
+ this option allows you to ignore the individual commits
+ brought in to your history by such a merge.
+
+--not::
+
+ Reverses the meaning of the '{caret}' prefix (or lack thereof)
+ for all following revision specifiers, up to the next '--not'.
+
+--all::
+
+ Pretend as if all the refs in `$GIT_DIR/refs/` are listed on the
+ command line as '<commit>'.
+
+--stdin::
+
+ In addition to the '<commit>' listed on the command
+ line, read them from the standard input.
+
+--quiet::
+
+ Don't print anything to standard output. This form
+ is primarily meant to allow the caller to
+ test the exit status to see if a range of objects is fully
+ connected (or not). It is faster than redirecting stdout
+ to /dev/null as the output does not have to be formatted.
+
+--cherry-pick::
+
+ Omit any commit that introduces the same change as
+ another commit on the "other side" when the set of
+ commits are limited with symmetric difference.
++
+For example, if you have two branches, `A` and `B`, a usual way
+to list all commits on only one side of them is with
+`--left-right`, like the example above in the description of
+that option. It however shows the commits that were cherry-picked
+from the other branch (for example, "3rd on b" may be cherry-picked
+from branch A). With this option, such pairs of commits are
+excluded from the output.
+
+-g, --walk-reflogs::
+
+ Instead of walking the commit ancestry chain, walk
+ reflog entries from the most recent one to older ones.
+ When this option is used you cannot specify commits to
+ exclude (that is, '{caret}commit', 'commit1..commit2',
+ nor 'commit1...commit2' notations cannot be used).
++
+With '\--pretty' format other than oneline (for obvious reasons),
+this causes the output to have two extra lines of information
+taken from the reflog. By default, 'commit@\{Nth}' notation is
+used in the output. When the starting commit is specified as
+'commit@{now}', output also uses 'commit@\{timestamp}' notation
+instead. Under '\--pretty=oneline', the commit message is
+prefixed with this information on the same line.
+
+Cannot be combined with '\--reverse'.
+See also linkgit:git-reflog[1].
+
+--merge::
+
+ After a failed merge, show refs that touch files having a
+ conflict and don't exist on all heads to merge.
+
+--boundary::
+
+ Output uninteresting commits at the boundary, which are usually
+ not shown.
+
+--dense, --sparse::
+
+When optional paths are given, the default behaviour ('--dense') is to
+only output commits that changes at least one of them, and also ignore
+merges that do not touch the given paths.
+
+Use the '--sparse' flag to makes the command output all eligible commits
+(still subject to count and age limitation), but apply merge
+simplification nevertheless.
+
+ifdef::git-rev-list[]
+--bisect::
+
+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 the two commands
+
+-----------------------------------------------------------------------
+ $ git-rev-list foo ^midpoint
+ $ 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.
+
+--bisect-vars::
+
+This calculates the same as `--bisect`, but outputs text ready
+to be eval'ed by the shell. These lines will assign the name of
+the midpoint revision to the variable `bisect_rev`, and the
+expected number of commits to be tested after `bisect_rev` is
+tested to `bisect_nr`, the expected number of commits to be
+tested if `bisect_rev` turns out to be good to `bisect_good`,
+the expected number of commits to be tested if `bisect_rev`
+turns out to be bad to `bisect_bad`, and the number of commits
+we are bisecting right now to `bisect_all`.
+
+--bisect-all::
+
+This outputs all the commit objects between the included and excluded
+commits, ordered by their distance to the included and excluded
+commits. The farthest from them is displayed first. (This is the only
+one displayed by `--bisect`.)
+
+This is useful because it makes it easy to choose a good commit to
+test when you want to avoid to test some of them for some reason (they
+may not compile for example).
+
+This option can be used along with `--bisect-vars`, in this case,
+after all the sorted commit objects, there will be the same text as if
+`--bisect-vars` had been used alone.
+endif::git-rev-list[]
+
+--
+
+Commit Ordering
+~~~~~~~~~~~~~~~
+
+By default, the commits are shown in reverse chronological order.
+
+--topo-order::
+
+ This option makes them appear in topological order (i.e.
+ descendant commits are shown before their parents).
+
+--date-order::
+
+ This option is similar to '--topo-order' in the sense that no
+ parent comes before all of its children, but otherwise things
+ are still ordered in the commit timestamp order.
+
+--reverse::
+
+ Output the commits in reverse order.
+ Cannot be combined with '\--walk-reflogs'.
+
+Object Traversal
+~~~~~~~~~~~~~~~~
+
+These options are mostly targeted for packing of git repositories.
+
+--objects::
+
+ Print the object IDs of any object referenced by the listed
+ commits. '--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'".
+
+--objects-edge::
+
+ Similar to '--objects', but also print the IDs of excluded
+ commits prefixed with a "-" character. This is used by
+ linkgit:git-pack-objects[1] to build "thin" pack, which records
+ objects in deltified form based on objects contained in these
+ excluded commits to reduce network traffic.
+
+--unpacked::
+
+ Only useful with '--objects'; print the object IDs that are not
+ in packs.
+
+--no-walk::
+
+ Only show the given revs, but do not traverse their ancestors.
+
+--do-walk::
+
+ Overrides a previous --no-walk.
projects / git.git / commitdiff