diff options
| author | Junio C Hamano <junio@kernel.org> | 2010-11-06 01:01:59 +0000 |
|---|---|---|
| committer | Junio C Hamano <junio@kernel.org> | 2010-11-06 01:01:59 +0000 |
| commit | 68cf15a825368c926443c26a6516947fca3c1d39 (patch) | |
| tree | a587c9a51372746ddc3cdb08108bb14fb94a0488 /git-rev-list.html | |
| parent | 39c7a69d994a13cbd5594bf2f5e65a0f21cc9bb9 (diff) | |
| download | git-htmldocs-68cf15a825368c926443c26a6516947fca3c1d39.tar.gz | |
Autogenerated HTML docs for v1.7.3.2-161-g3089c
Diffstat (limited to 'git-rev-list.html')
| -rw-r--r-- | git-rev-list.html | 537 |
1 files changed, 316 insertions, 221 deletions
diff --git a/git-rev-list.html b/git-rev-list.html index 3fe9dc3ed..8de7aa49b 100644 --- a/git-rev-list.html +++ b/git-rev-list.html @@ -3,7 +3,8 @@ <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
-<meta name="generator" content="AsciiDoc 8.2.5" />
+<meta name="generator" content="AsciiDoc 8.4.5" />
+<title>git-rev-list(1)</title>
<style type="text/css">
/* Debug borders */
p, li, dt, dd, div, pre, h1, h2, h3, h4, h5, h6 {
@@ -26,10 +27,12 @@ a:visited { em {
font-style: italic;
+ color: navy;
}
strong {
font-weight: bold;
+ color: #083194;
}
tt {
@@ -71,6 +74,10 @@ p { margin-bottom: 0.5em;
}
+ul, ol, li > p {
+ margin-top: 0;
+}
+
pre {
padding: 0;
margin: 0;
@@ -84,7 +91,7 @@ span#author { }
span#email {
}
-span#revision {
+span#revnumber, span#revdate, span#revremark {
font-family: sans-serif;
}
@@ -104,11 +111,13 @@ div#footer-badges { padding-bottom: 0.5em;
}
-div#preamble,
+div#preamble {
+ margin-top: 1.5em;
+ margin-bottom: 1.5em;
+}
div.tableblock, div.imageblock, div.exampleblock, div.verseblock,
div.quoteblock, div.literalblock, div.listingblock, div.sidebarblock,
div.admonitionblock {
- margin-right: 10%;
margin-top: 1.5em;
margin-bottom: 1.5em;
}
@@ -123,6 +132,7 @@ div.content { /* Block element content. */ /* Block element titles. */
div.title, caption.title {
+ color: #527bbd;
font-family: sans-serif;
font-weight: bold;
text-align: left;
@@ -149,22 +159,33 @@ div.sidebarblock > div.content { padding: 0.5em;
}
-div.listingblock {
- margin-right: 0%;
-}
div.listingblock > div.content {
border: 1px solid silver;
background: #f4f4f4;
padding: 0.5em;
}
-div.quoteblock > div.content {
+div.quoteblock {
padding-left: 2.0em;
+ margin-right: 10%;
}
-
-div.attribution {
+div.quoteblock > div.attribution {
+ padding-top: 0.5em;
text-align: right;
}
+
+div.verseblock {
+ padding-left: 2.0em;
+ margin-right: 10%;
+}
+div.verseblock > div.content {
+ white-space: pre;
+}
+div.verseblock > div.attribution {
+ padding-top: 0.75em;
+ text-align: left;
+}
+/* DEPRECATED: Pre version 8.2.7 verse style literal block. */
div.verseblock + div.attribution {
text-align: left;
}
@@ -187,13 +208,9 @@ div.exampleblock > div.content { padding: 0.5em;
}
-div.verseblock div.content {
- white-space: pre;
-}
-
div.imageblock div.content { padding-left: 0; }
-div.imageblock img { border: 1px solid silver; }
span.image img { border-style: none; }
+a.image:visited { color: white; }
dl {
margin-top: 0.8em;
@@ -202,18 +219,38 @@ dl { dt {
margin-top: 0.5em;
margin-bottom: 0;
- font-style: italic;
+ font-style: normal;
+ color: navy;
}
dd > *:first-child {
- margin-top: 0;
+ margin-top: 0.1em;
}
ul, ol {
list-style-position: outside;
}
-div.olist2 ol {
+ol.arabic {
+ list-style-type: decimal;
+}
+ol.loweralpha {
list-style-type: lower-alpha;
}
+ol.upperalpha {
+ list-style-type: upper-alpha;
+}
+ol.lowerroman {
+ list-style-type: lower-roman;
+}
+ol.upperroman {
+ list-style-type: upper-roman;
+}
+
+div.compact ul, div.compact ol,
+div.compact p, div.compact p,
+div.compact div, div.compact div {
+ margin-top: 0.1em;
+ margin-bottom: 0.1em;
+}
div.tableblock > table {
border: 3px solid #527bbd;
@@ -225,22 +262,53 @@ thead { tfoot {
font-weight: bold;
}
+td > div.verse {
+ white-space: pre;
+}
+p.table {
+ margin-top: 0;
+}
+/* Because the table frame attribute is overriden by CSS in most browsers. */
+div.tableblock > table[frame="void"] {
+ border-style: none;
+}
+div.tableblock > table[frame="hsides"] {
+ border-left-style: none;
+ border-right-style: none;
+}
+div.tableblock > table[frame="vsides"] {
+ border-top-style: none;
+ border-bottom-style: none;
+}
+
-div.hlist {
+div.hdlist {
margin-top: 0.8em;
margin-bottom: 0.8em;
}
-div.hlist td {
- padding-bottom: 5px;
+div.hdlist tr {
+ padding-bottom: 15px;
+}
+dt.hdlist1.strong, td.hdlist1.strong {
+ font-weight: bold;
}
-td.hlist1 {
+td.hdlist1 {
vertical-align: top;
- font-style: italic;
+ font-style: normal;
padding-right: 0.8em;
+ color: navy;
}
-td.hlist2 {
+td.hdlist2 {
vertical-align: top;
}
+div.hdlist.compact tr {
+ margin: 0;
+ padding-bottom: 0;
+}
+
+.comment {
+ background: yellow;
+}
@media print {
div#footer-badges { display: none; }
@@ -271,7 +339,24 @@ div.toclevel4 { margin-left: 6em;
font-size: 0.9em;
}
-include1::./stylesheets/xhtml11-manpage.css[]
+/* Overrides for manpage documents */
+h1 {
+ padding-top: 0.5em;
+ padding-bottom: 0.5em;
+ border-top: 2px solid silver;
+ border-bottom: 2px solid silver;
+}
+h2 {
+ border-style: none;
+}
+div.sectionbody {
+ margin-left: 5%;
+}
+
+@media print {
+ div#toc { display: none; }
+}
+
/* Workarounds for IE6's broken and incomplete CSS2. */
div.sidebar-content {
@@ -280,6 +365,7 @@ div.sidebar-content { padding: 0.5em;
}
div.sidebar-title, div.image-title {
+ color: #527bbd;
font-family: sans-serif;
font-weight: bold;
margin-top: 0.0em;
@@ -292,8 +378,17 @@ div.listingblock div.content { padding: 0.5em;
}
-div.quoteblock-content {
- padding-left: 2.0em;
+div.quoteblock-attribution {
+ padding-top: 0.5em;
+ text-align: right;
+}
+
+div.verseblock-content {
+ white-space: pre;
+}
+div.verseblock-attribution {
+ padding-top: 0.75em;
+ text-align: left;
}
div.exampleblock-content {
@@ -304,7 +399,6 @@ div.exampleblock-content { /* IE6 sets dynamically generated links as visited. */
div#toc a:visited { color: blue; }
</style>
-<title>git-rev-list(1)</title>
</head>
<body>
<div id="header">
@@ -318,10 +412,10 @@ git-rev-list(1) Manual Page </p>
</div>
</div>
-<h2>SYNOPSIS</h2>
+<h2 id="_synopsis">SYNOPSIS</h2>
<div class="sectionbody">
<div class="verseblock">
-<div class="content"><em>git rev-list</em> [ --max-count=<number> ]
+<div class="verseblock-content"><em>git rev-list</em> [ --max-count=<number> ]
[ --skip=<number> ]
[ --max-age=<timestamp> ]
[ --min-age=<timestamp> ]
@@ -359,28 +453,30 @@ git-rev-list(1) Manual Page [ --reverse ]
[ --walk-reflogs ]
[ --no-walk ] [ --do-walk ]
- <commit>… [ -- <paths>… ]</div></div>
+ <commit>… [ -- <paths>… ]</div>
+<div class="verseblock-attribution">
+</div></div>
</div>
<h2 id="_description">DESCRIPTION</h2>
<div class="sectionbody">
-<div class="para"><p>List commits that are reachable by following the <tt>parent</tt> links from the
+<div class="paragraph"><p>List commits that are reachable by following the <tt>parent</tt> links from the
given commit(s), but exclude commits that are reachable from the one(s)
given with a <em>^</em> in front of them. The output is given in reverse
chronological order by default.</p></div>
-<div class="para"><p>You can think of this as a set operation. Commits given on the command
+<div class="paragraph"><p>You can think of this as a set operation. Commits given on the command
line form a set of commits that are reachable from any of them, and then
commits reachable from any of the ones given with <em>^</em> in front are
subtracted from that set. The remaining commits are what comes out in the
-command's output. Various other options and paths parameters can be used
+command’s output. Various other options and paths parameters can be used
to further limit the result.</p></div>
-<div class="para"><p>Thus, the following command:</p></div>
+<div class="paragraph"><p>Thus, the following command:</p></div>
<div class="listingblock">
<div class="content">
<pre><tt> $ git rev-list foo bar ^baz</tt></pre>
</div></div>
-<div class="para"><p>means "list all the commits which are reachable from <em>foo</em> or <em>bar</em>, but
+<div class="paragraph"><p>means "list all the commits which are reachable from <em>foo</em> or <em>bar</em>, but
not from <em>baz</em>".</p></div>
-<div class="para"><p>A special notation "<em><commit1></em>..<em><commit2></em>" can be used as a
+<div class="paragraph"><p>A special notation "<em><commit1></em>..<em><commit2></em>" can be used as a
short-hand for "^<em><commit1></em> <em><commit2></em>". For example, either of
the following may be used interchangeably:</p></div>
<div class="listingblock">
@@ -388,7 +484,7 @@ the following may be used interchangeably:</p></div> <pre><tt> $ git rev-list origin..HEAD
$ git rev-list HEAD ^origin</tt></pre>
</div></div>
-<div class="para"><p>Another special notation is "<em><commit1></em>…<em><commit2></em>" which is useful
+<div class="paragraph"><p>Another special notation is "<em><commit1></em>…<em><commit2></em>" which is useful
for merges. The resulting set of commits is the symmetric difference
between the two operands. The following two commands are equivalent:</p></div>
<div class="listingblock">
@@ -396,7 +492,7 @@ between the two operands. The following two commands are equivalent:</p></div> <pre><tt> $ git rev-list A B --not $(git merge-base --all A B)
$ git rev-list A...B</tt></pre>
</div></div>
-<div class="para"><p><em>rev-list</em> is a very essential git command, since it
+<div class="paragraph"><p><em>rev-list</em> is a very essential git command, since it
provides the ability to build and traverse commit ancestry graphs. For
this reason, it has a lot of different options that enables it to be
used by commands as different as <em>git bisect</em> and
@@ -405,14 +501,14 @@ used by commands as different as <em>git bisect</em> and <h2 id="_options">OPTIONS</h2>
<div class="sectionbody">
<h3 id="_commit_formatting">Commit Formatting</h3><div style="clear:left"></div>
-<div class="para"><p>Using these options, <a href="git-rev-list.html">git-rev-list(1)</a> will act similar to the
+<div class="paragraph"><p>Using these options, <a href="git-rev-list.html">git-rev-list(1)</a> will act similar to the
more specialized family of commit log tools: <a href="git-log.html">git-log(1)</a>,
<a href="git-show.html">git-show(1)</a>, and <a href="git-whatchanged.html">git-whatchanged(1)</a></p></div>
-<div class="vlist"><dl>
-<dt>
+<div class="dlist"><dl>
+<dt class="hdlist1">
--pretty[=<format>]
</dt>
-<dt>
+<dt class="hdlist1">
--format=<format>
</dt>
<dd>
@@ -423,10 +519,10 @@ more specialized family of commit log tools: <a href="git-log.html">git-log(1)</ the "PRETTY FORMATS" section for some additional details for each
format. When omitted, the format defaults to <em>medium</em>.
</p>
-<div class="para"><p>Note: you can specify the default pretty format in the repository
+<div class="paragraph"><p>Note: you can specify the default pretty format in the repository
configuration (see <a href="git-config.html">git-config(1)</a>).</p></div>
</dd>
-<dt>
+<dt class="hdlist1">
--abbrev-commit
</dt>
<dd>
@@ -436,10 +532,10 @@ configuration (see <a href="git-config.html">git-config(1)</a>).</p></div> digits can be specified with "--abbrev=<n>" (which also modifies
diff output, if it is displayed).
</p>
-<div class="para"><p>This should make "--pretty=oneline" a whole lot more readable for
+<div class="paragraph"><p>This should make "--pretty=oneline" a whole lot more readable for
people using 80-column terminals.</p></div>
</dd>
-<dt>
+<dt class="hdlist1">
--oneline
</dt>
<dd>
@@ -448,7 +544,7 @@ people using 80-column terminals.</p></div> used together.
</p>
</dd>
-<dt>
+<dt class="hdlist1">
--encoding[=<encoding>]
</dt>
<dd>
@@ -460,10 +556,10 @@ people using 80-column terminals.</p></div> defaults to UTF-8.
</p>
</dd>
-<dt>
+<dt class="hdlist1">
--no-notes
</dt>
-<dt>
+<dt class="hdlist1">
--show-notes[=<ref>]
</dt>
<dd>
@@ -474,10 +570,10 @@ people using 80-column terminals.</p></div> there is no <tt>--pretty</tt>, <tt>--format</tt> nor <tt>--oneline</tt> option is
given on the command line.
</p>
-<div class="para"><p>With an optional argument, add this ref to the list of notes. The ref
+<div class="paragraph"><p>With an optional argument, add this ref to the list of notes. The ref
is taken to be in <tt>refs/notes/</tt> if it is not qualified.</p></div>
</dd>
-<dt>
+<dt class="hdlist1">
--[no-]standard-notes
</dt>
<dd>
@@ -488,7 +584,7 @@ is taken to be in <tt>refs/notes/</tt> if it is not qualified.</p></div> See <a href="git-config.html">git-config(1)</a>.
</p>
</dd>
-<dt>
+<dt class="hdlist1">
--relative-date
</dt>
<dd>
@@ -496,27 +592,27 @@ is taken to be in <tt>refs/notes/</tt> if it is not qualified.</p></div> Synonym for <tt>--date=relative</tt>.
</p>
</dd>
-<dt>
+<dt class="hdlist1">
--date=(relative|local|default|iso|rfc|short|raw)
</dt>
<dd>
<p>
Only takes effect for dates shown in human-readable format, such
as when using "--pretty". <tt>log.date</tt> config variable sets a default
- value for log command's --date option.
+ value for log command’s --date option.
</p>
-<div class="para"><p><tt>--date=relative</tt> shows dates relative to the current time,
+<div class="paragraph"><p><tt>--date=relative</tt> shows dates relative to the current time,
e.g. "2 hours ago".</p></div>
-<div class="para"><p><tt>--date=local</tt> shows timestamps in user's local timezone.</p></div>
-<div class="para"><p><tt>--date=iso</tt> (or <tt>--date=iso8601</tt>) shows timestamps in ISO 8601 format.</p></div>
-<div class="para"><p><tt>--date=rfc</tt> (or <tt>--date=rfc2822</tt>) shows timestamps in RFC 2822
+<div class="paragraph"><p><tt>--date=local</tt> shows timestamps in user’s local timezone.</p></div>
+<div class="paragraph"><p><tt>--date=iso</tt> (or <tt>--date=iso8601</tt>) shows timestamps in ISO 8601 format.</p></div>
+<div class="paragraph"><p><tt>--date=rfc</tt> (or <tt>--date=rfc2822</tt>) shows timestamps in RFC 2822
format, often found in E-mail messages.</p></div>
-<div class="para"><p><tt>--date=short</tt> shows only date but not time, in <tt>YYYY-MM-DD</tt> format.</p></div>
-<div class="para"><p><tt>--date=raw</tt> shows the date in the internal raw git format <tt>%s %z</tt> format.</p></div>
-<div class="para"><p><tt>--date=default</tt> shows timestamps in the original timezone
-(either committer's or author's).</p></div>
+<div class="paragraph"><p><tt>--date=short</tt> shows only date but not time, in <tt>YYYY-MM-DD</tt> format.</p></div>
+<div class="paragraph"><p><tt>--date=raw</tt> shows the date in the internal raw git format <tt>%s %z</tt> format.</p></div>
+<div class="paragraph"><p><tt>--date=default</tt> shows timestamps in the original timezone
+(either committer’s or author’s).</p></div>
</dd>
-<dt>
+<dt class="hdlist1">
--header
</dt>
<dd>
@@ -525,7 +621,7 @@ format, often found in E-mail messages.</p></div> separated with a NUL character.
</p>
</dd>
-<dt>
+<dt class="hdlist1">
--parents
</dt>
<dd>
@@ -534,7 +630,7 @@ format, often found in E-mail messages.</p></div> Also enables parent rewriting, see <em>History Simplification</em> below.
</p>
</dd>
-<dt>
+<dt class="hdlist1">
--children
</dt>
<dd>
@@ -543,7 +639,7 @@ format, often found in E-mail messages.</p></div> Also enables parent rewriting, see <em>History Simplification</em> below.
</p>
</dd>
-<dt>
+<dt class="hdlist1">
--timestamp
</dt>
<dd>
@@ -551,7 +647,7 @@ format, often found in E-mail messages.</p></div> Print the raw commit timestamp.
</p>
</dd>
-<dt>
+<dt class="hdlist1">
--left-right
</dt>
<dd>
@@ -561,7 +657,7 @@ format, often found in E-mail messages.</p></div> the right with <tt>></tt>. If combined with <tt>--boundary</tt>, those
commits are prefixed with <tt>-</tt>.
</p>
-<div class="para"><p>For example, if you have this topology:</p></div>
+<div class="paragraph"><p>For example, if you have this topology:</p></div>
<div class="listingblock">
<div class="content">
<pre><tt> y---b---b branch B
@@ -570,7 +666,7 @@ format, often found in E-mail messages.</p></div> / / \
o---x---a---a branch A</tt></pre>
</div></div>
-<div class="para"><p>you would get an output like this:</p></div>
+<div class="paragraph"><p>you would get an output like this:</p></div>
<div class="listingblock">
<div class="content">
<pre><tt> $ git rev-list --left-right --boundary --pretty=oneline A...B
@@ -583,7 +679,7 @@ format, often found in E-mail messages.</p></div> -xxxxxxx... 1st on a</tt></pre>
</div></div>
</dd>
-<dt>
+<dt class="hdlist1">
--graph
</dt>
<dd>
@@ -593,10 +689,10 @@ format, often found in E-mail messages.</p></div> to be printed in between commits, in order for the graph history
to be drawn properly.
</p>
-<div class="para"><p>This implies the <em>--topo-order</em> option by default, but the
+<div class="paragraph"><p>This implies the <em>--topo-order</em> option by default, but the
<em>--date-order</em> option may also be specified.</p></div>
</dd>
-<dt>
+<dt class="hdlist1">
--count
</dt>
<dd>
@@ -609,14 +705,14 @@ format, often found in E-mail messages.</p></div> </dd>
</dl></div>
<h3 id="_commit_limiting">Commit Limiting</h3><div style="clear:left"></div>
-<div class="para"><p>Besides specifying a range of commits that should be listed using the
+<div class="paragraph"><p>Besides specifying a range of commits that should be listed using the
special notations explained in the description, additional commit
limiting may be applied.</p></div>
-<div class="vlist"><dl>
-<dt>
+<div class="dlist"><dl>
+<dt class="hdlist1">
-n <em>number</em>
</dt>
-<dt>
+<dt class="hdlist1">
--max-count=<number>
</dt>
<dd>
@@ -624,7 +720,7 @@ limiting may be applied.</p></div> Limit the number of commits output.
</p>
</dd>
-<dt>
+<dt class="hdlist1">
--skip=<number>
</dt>
<dd>
@@ -632,10 +728,10 @@ limiting may be applied.</p></div> Skip <em>number</em> commits before starting to show the commit output.
</p>
</dd>
-<dt>
+<dt class="hdlist1">
--since=<date>
</dt>
-<dt>
+<dt class="hdlist1">
--after=<date>
</dt>
<dd>
@@ -643,10 +739,10 @@ limiting may be applied.</p></div> Show commits more recent than a specific date.
</p>
</dd>
-<dt>
+<dt class="hdlist1">
--until=<date>
</dt>
-<dt>
+<dt class="hdlist1">
--before=<date>
</dt>
<dd>
@@ -654,10 +750,10 @@ limiting may be applied.</p></div> Show commits older than a specific date.
</p>
</dd>
-<dt>
+<dt class="hdlist1">
--max-age=<timestamp>
</dt>
-<dt>
+<dt class="hdlist1">
--min-age=<timestamp>
</dt>
<dd>
@@ -665,10 +761,10 @@ limiting may be applied.</p></div> Limit the commits output to specified time range.
</p>
</dd>
-<dt>
+<dt class="hdlist1">
--author=<pattern>
</dt>
-<dt>
+<dt class="hdlist1">
--committer=<pattern>
</dt>
<dd>
@@ -677,7 +773,7 @@ limiting may be applied.</p></div> header lines that match the specified pattern (regular expression).
</p>
</dd>
-<dt>
+<dt class="hdlist1">
--grep=<pattern>
</dt>
<dd>
@@ -686,7 +782,7 @@ limiting may be applied.</p></div> matches the specified pattern (regular expression).
</p>
</dd>
-<dt>
+<dt class="hdlist1">
--all-match
</dt>
<dd>
@@ -695,10 +791,10 @@ limiting may be applied.</p></div> --author and --committer instead of ones that match at least one.
</p>
</dd>
-<dt>
+<dt class="hdlist1">
-i
</dt>
-<dt>
+<dt class="hdlist1">
--regexp-ignore-case
</dt>
<dd>
@@ -706,10 +802,10 @@ limiting may be applied.</p></div> Match the regexp limiting patterns without regard to letters case.
</p>
</dd>
-<dt>
+<dt class="hdlist1">
-E
</dt>
-<dt>
+<dt class="hdlist1">
--extended-regexp
</dt>
<dd>
@@ -718,19 +814,19 @@ limiting may be applied.</p></div> instead of the default basic regular expressions.
</p>
</dd>
-<dt>
+<dt class="hdlist1">
-F
</dt>
-<dt>
+<dt class="hdlist1">
--fixed-strings
</dt>
<dd>
<p>
- Consider the limiting patterns to be fixed strings (don't interpret
+ Consider the limiting patterns to be fixed strings (don’t interpret
pattern as a regular expression).
</p>
</dd>
-<dt>
+<dt class="hdlist1">
--remove-empty
</dt>
<dd>
@@ -738,7 +834,7 @@ limiting may be applied.</p></div> Stop when a given path disappears from the tree.
</p>
</dd>
-<dt>
+<dt class="hdlist1">
--merges
</dt>
<dd>
@@ -746,7 +842,7 @@ limiting may be applied.</p></div> Print only merge commits.
</p>
</dd>
-<dt>
+<dt class="hdlist1">
--no-merges
</dt>
<dd>
@@ -754,7 +850,7 @@ limiting may be applied.</p></div> Do not print commits with more than one parent.
</p>
</dd>
-<dt>
+<dt class="hdlist1">
--first-parent
</dt>
<dd>
@@ -768,7 +864,7 @@ limiting may be applied.</p></div> brought in to your history by such a merge.
</p>
</dd>
-<dt>
+<dt class="hdlist1">
--not
</dt>
<dd>
@@ -777,7 +873,7 @@ limiting may be applied.</p></div> for all following revision specifiers, up to the next <em>--not</em>.
</p>
</dd>
-<dt>
+<dt class="hdlist1">
--all
</dt>
<dd>
@@ -786,7 +882,7 @@ limiting may be applied.</p></div> command line as <em><commit></em>.
</p>
</dd>
-<dt>
+<dt class="hdlist1">
--branches[=<pattern>]
</dt>
<dd>
@@ -797,7 +893,7 @@ limiting may be applied.</p></div> <em><strong></em>, or <em>[</em>, <em>/</strong></em> at the end is implied.
</p>
</dd>
-<dt>
+<dt class="hdlist1">
--tags[=<pattern>]
</dt>
<dd>
@@ -808,7 +904,7 @@ limiting may be applied.</p></div> or <em>[</em>, <em>/</strong></em> at the end is implied.
</p>
</dd>
-<dt>
+<dt class="hdlist1">
--remotes[=<pattern>]
</dt>
<dd>
@@ -819,7 +915,7 @@ limiting may be applied.</p></div> If pattern lacks <em>?</em>, <em><strong></em>, or <em>[</em>, <em>/</strong></em> at the end is implied.
</p>
</dd>
-<dt>
+<dt class="hdlist1">
--glob=<glob-pattern>
</dt>
<dd>
@@ -830,7 +926,7 @@ limiting may be applied.</p></div> or <em>[</em>, <em>/</strong></em> at the end is implied.
</p>
</dd>
-<dt>
+<dt class="hdlist1">
--stdin
</dt>
<dd>
@@ -841,39 +937,39 @@ limiting may be applied.</p></div> result.
</p>
</dd>
-<dt>
+<dt class="hdlist1">
--quiet
</dt>
<dd>
<p>
- Don't print anything to standard output. This form
+ 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.
</p>
</dd>
-<dt>
+<dt class="hdlist1">
--cherry-pick
</dt>
<dd>
<p>
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.<br />
-For example, if you have two branches, <tt>A</tt> and <tt>B</tt>, a usual way
+ commits are limited with symmetric difference.
+</p>
+<div class="paragraph"><p>For example, if you have two branches, <tt>A</tt> and <tt>B</tt>, a usual way
to list all commits on only one side of them is with
<tt>--left-right</tt>, 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.
-</p>
+excluded from the output.</p></div>
</dd>
-<dt>
+<dt class="hdlist1">
-g
</dt>
-<dt>
+<dt class="hdlist1">
--walk-reflogs
</dt>
<dd>
@@ -882,8 +978,9 @@ excluded from the output. reflog entries from the most recent one to older ones.
When this option is used you cannot specify commits to
exclude (that is, <em>^commit</em>, <em>commit1..commit2</em>,
- nor <em>commit1...commit2</em> notations cannot be used).<br />
-With <em>--pretty</em> format other than oneline (for obvious reasons),
+ nor <em>commit1...commit2</em> notations cannot be used).
+</p>
+<div class="paragraph"><p>With <em>--pretty</em> format other than oneline (for obvious reasons),
this causes the output to have two extra lines of information
taken from the reflog. By default, <em>commit@{Nth}</em> notation is
used in the output. When the starting commit is specified as
@@ -891,19 +988,18 @@ used in the output. When the starting commit is specified as instead. Under <em>--pretty=oneline</em>, the commit message is
prefixed with this information on the same line.
This option cannot be combined with <em>--reverse</em>.
-See also <a href="git-reflog.html">git-reflog(1)</a>.
-</p>
+See also <a href="git-reflog.html">git-reflog(1)</a>.</p></div>
</dd>
-<dt>
+<dt class="hdlist1">
--merge
</dt>
<dd>
<p>
After a failed merge, show refs that touch files having a
- conflict and don't exist on all heads to merge.
+ conflict and don’t exist on all heads to merge.
</p>
</dd>
-<dt>
+<dt class="hdlist1">
--boundary
</dt>
<dd>
@@ -914,13 +1010,13 @@ See also <a href="git-reflog.html">git-reflog(1)</a>. </dd>
</dl></div>
<h3 id="_history_simplification">History Simplification</h3><div style="clear:left"></div>
-<div class="para"><p>Sometimes you are only interested in parts of the history, for example the
+<div class="paragraph"><p>Sometimes you are only interested in parts of the history, for example the
commits modifying a particular <path>. But there are two parts of
<em>History Simplification</em>, one part is selecting the commits and the other
is how to do it, as there are various strategies to simplify the history.</p></div>
-<div class="para"><p>The following options select the commits to be shown:</p></div>
-<div class="vlist"><dl>
-<dt>
+<div class="paragraph"><p>The following options select the commits to be shown:</p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
<paths>
</dt>
<dd>
@@ -928,7 +1024,7 @@ is how to do it, as there are various strategies to simplify the history.</p></d Commits modifying the given <paths> are selected.
</p>
</dd>
-<dt>
+<dt class="hdlist1">
--simplify-by-decoration
</dt>
<dd>
@@ -937,10 +1033,10 @@ is how to do it, as there are various strategies to simplify the history.</p></d </p>
</dd>
</dl></div>
-<div class="para"><p>Note that extra commits can be shown to give a meaningful history.</p></div>
-<div class="para"><p>The following options affect the way the simplification is performed:</p></div>
-<div class="vlist"><dl>
-<dt>
+<div class="paragraph"><p>Note that extra commits can be shown to give a meaningful history.</p></div>
+<div class="paragraph"><p>The following options affect the way the simplification is performed:</p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
Default mode
</dt>
<dd>
@@ -951,7 +1047,7 @@ Default mode with the same content)
</p>
</dd>
-<dt>
+<dt class="hdlist1">
--full-history
</dt>
<dd>
@@ -959,7 +1055,7 @@ Default mode As the default mode but does not prune some history.
</p>
</dd>
-<dt>
+<dt class="hdlist1">
--dense
</dt>
<dd>
@@ -968,7 +1064,7 @@ Default mode meaningful history.
</p>
</dd>
-<dt>
+<dt class="hdlist1">
--sparse
</dt>
<dd>
@@ -976,7 +1072,7 @@ Default mode All commits in the simplified history are shown.
</p>
</dd>
-<dt>
+<dt class="hdlist1">
--simplify-merges
</dt>
<dd>
@@ -986,7 +1082,7 @@ Default mode commits contributing to this merge.
</p>
</dd>
-<dt>
+<dt class="hdlist1">
--ancestry-path
</dt>
<dd>
@@ -999,11 +1095,11 @@ Default mode </p>
</dd>
</dl></div>
-<div class="para"><p>A more detailed explanation follows.</p></div>
-<div class="para"><p>Suppose you specified <tt>foo</tt> as the <paths>. We shall call commits
+<div class="paragraph"><p>A more detailed explanation follows.</p></div>
+<div class="paragraph"><p>Suppose you specified <tt>foo</tt> as the <paths>. We shall call commits
that modify <tt>foo</tt> !TREESAME, and the rest TREESAME. (In a diff
filtered for <tt>foo</tt>, they look different and equal, respectively.)</p></div>
-<div class="para"><p>In the following, we will always refer to the same example history to
+<div class="paragraph"><p>In the following, we will always refer to the same example history to
illustrate the differences between simplification settings. We assume
that you are filtering for a file <tt>foo</tt> in this commit graph:</p></div>
<div class="listingblock">
@@ -1014,9 +1110,9 @@ that you are filtering for a file <tt>foo</tt> in this commit graph:</p></div> \ / / / /
`-------------'</tt></pre>
</div></div>
-<div class="para"><p>The horizontal line of history A--P is taken to be the first parent of
+<div class="paragraph"><p>The horizontal line of history A—P is taken to be the first parent of
each merge. The commits are:</p></div>
-<div class="ilist"><ul>
+<div class="ulist"><ul>
<li>
<p>
<tt>I</tt> is the initial commit, in which <tt>foo</tt> exists with contents
@@ -1055,12 +1151,12 @@ In <tt>A</tt>, <tt>foo</tt> contains just "foo". </p>
</li>
</ul></div>
-<div class="para"><p><em>rev-list</em> walks backwards through history, including or excluding
+<div class="paragraph"><p><em>rev-list</em> walks backwards through history, including or excluding
commits based on whether <em>--full-history</em> and/or parent rewriting
(via <em>--parents</em> or <em>--children</em>) are used. The following settings
are available.</p></div>
-<div class="vlist"><dl>
-<dt>
+<div class="dlist"><dl>
+<dt class="hdlist1">
Default mode
</dt>
<dd>
@@ -1072,22 +1168,22 @@ Default mode parents, follow only one of them.) Otherwise, follow all
parents.
</p>
-<div class="para"><p>This results in:</p></div>
+<div class="paragraph"><p>This results in:</p></div>
<div class="listingblock">
<div class="content">
<pre><tt> .-A---N---O
/ / /
I---------D</tt></pre>
</div></div>
-<div class="para"><p>Note how the rule to only follow the TREESAME parent, if one is
+<div class="paragraph"><p>Note how the rule to only follow the TREESAME parent, if one is
available, removed <tt>B</tt> from consideration entirely. <tt>C</tt> was
considered via <tt>N</tt>, but is TREESAME. Root commits are compared to an
empty tree, so <tt>I</tt> is !TREESAME.</p></div>
-<div class="para"><p>Parent/child relations are only visible with --parents, but that does
+<div class="paragraph"><p>Parent/child relations are only visible with --parents, but that does
not affect the commits selected in default mode, so we have shown the
parent lines.</p></div>
</dd>
-<dt>
+<dt class="hdlist1">
--full-history without parent rewriting
</dt>
<dd>
@@ -1102,14 +1198,14 @@ parent lines.</p></div> <div class="content">
<pre><tt> I A B N D O</tt></pre>
</div></div>
-<div class="para"><p><tt>P</tt> and <tt>M</tt> were excluded because they are TREESAME to a parent. <tt>E</tt>,
+<div class="paragraph"><p><tt>P</tt> and <tt>M</tt> were excluded because they are TREESAME to a parent. <tt>E</tt>,
<tt>C</tt> and <tt>B</tt> were all walked, but only <tt>B</tt> was !TREESAME, so the others
do not appear.</p></div>
-<div class="para"><p>Note that without parent rewriting, it is not really possible to talk
+<div class="paragraph"><p>Note that without parent rewriting, it is not really possible to talk
about the parent/child relationships between the commits, so we show
them disconnected.</p></div>
</dd>
-<dt>
+<dt class="hdlist1">
--full-history with parent rewriting
</dt>
<dd>
@@ -1117,7 +1213,7 @@ them disconnected.</p></div> Ordinary commits are only included if they are !TREESAME
(though this can be changed, see <em>--sparse</em> below).
</p>
-<div class="para"><p>Merges are always included. However, their parent list is rewritten:
+<div class="paragraph"><p>Merges are always included. However, their parent list is rewritten:
Along each parent, prune away commits that are not included
themselves. This results in</p></div>
<div class="listingblock">
@@ -1128,16 +1224,16 @@ themselves. This results in</p></div> \ / / / /
`-------------'</tt></pre>
</div></div>
-<div class="para"><p>Compare to <em>--full-history</em> without rewriting above. Note that <tt>E</tt>
+<div class="paragraph"><p>Compare to <em>--full-history</em> without rewriting above. Note that <tt>E</tt>
was pruned away because it is TREESAME, but the parent list of P was
rewritten to contain <tt>E</tt>'s parent <tt>I</tt>. The same happened for <tt>C</tt> and
<tt>N</tt>. Note also that <tt>P</tt> was included despite being TREESAME.</p></div>
</dd>
</dl></div>
-<div class="para"><p>In addition to the above settings, you can change whether TREESAME
+<div class="paragraph"><p>In addition to the above settings, you can change whether TREESAME
affects inclusion:</p></div>
-<div class="vlist"><dl>
-<dt>
+<div class="dlist"><dl>
+<dt class="hdlist1">
--dense
</dt>
<dd>
@@ -1146,18 +1242,18 @@ affects inclusion:</p></div> to any parent.
</p>
</dd>
-<dt>
+<dt class="hdlist1">
--sparse
</dt>
<dd>
<p>
All commits that are walked are included.
</p>
-<div class="para"><p>Note that without <em>--full-history</em>, this still simplifies merges: if
+<div class="paragraph"><p>Note that without <em>--full-history</em>, this still simplifies merges: if
one of the parents is TREESAME, we follow only that one, so the other
sides of the merge are never walked.</p></div>
</dd>
-<dt>
+<dt class="hdlist1">
--simplify-merges
</dt>
<dd>
@@ -1165,30 +1261,30 @@ sides of the merge are never walked.</p></div> First, build a history graph in the same way that
<em>--full-history</em> with parent rewriting does (see above).
</p>
-<div class="para"><p>Then simplify each commit <tt>C</tt> to its replacement <tt>C'</tt> in the final
+<div class="paragraph"><p>Then simplify each commit ‘C` to its replacement <tt>C’</tt> in the final
history according to the following rules:</p></div>
-<div class="ilist"><ul>
+<div class="ulist"><ul>
<li>
<p>
-Set <tt>C'</tt> to <tt>C</tt>.<br />
+Set ‘C’` to <tt>C</tt>.
</p>
</li>
<li>
<p>
-Replace each parent <tt>P</tt> of <tt>C'</tt> with its simplification <tt>P'</tt>. In
+Replace each parent ‘P` of <tt>C’</tt> with its simplification ‘P’`. In
the process, drop parents that are ancestors of other parents, and
- remove duplicates.<br />
+ remove duplicates.
</p>
</li>
<li>
<p>
-If after this parent rewriting, <tt>C'</tt> is a root or merge commit (has
+If after this parent rewriting, ‘C’` is a root or merge commit (has
zero or >1 parents), a boundary commit, or !TREESAME, it remains.
Otherwise, it is replaced with its only parent.
</p>
</li>
</ul></div>
-<div class="para"><p>The effect of this is best shown by way of comparing to
+<div class="paragraph"><p>The effect of this is best shown by way of comparing to
<em>--full-history</em> with parent rewriting. The example turns into:</p></div>
<div class="listingblock">
<div class="content">
@@ -1198,12 +1294,12 @@ If after this parent rewriting, <tt>C'</tt> is a root or merge commit (has \ / /
`---------'</tt></pre>
</div></div>
-<div class="para"><p>Note the major differences in <tt>N</tt> and <tt>P</tt> over <em>--full-history</em>:</p></div>
-<div class="ilist"><ul>
+<div class="paragraph"><p>Note the major differences in <tt>N</tt> and <tt>P</tt> over <em>--full-history</em>:</p></div>
+<div class="ulist"><ul>
<li>
<p>
<tt>N</tt>'s parent list had <tt>I</tt> removed, because it is an ancestor of the
- other parent <tt>M</tt>. Still, <tt>N</tt> remained because it is !TREESAME.<br />
+ other parent <tt>M</tt>. Still, <tt>N</tt> remained because it is !TREESAME.
</p>
</li>
<li>
@@ -1215,9 +1311,9 @@ If after this parent rewriting, <tt>C'</tt> is a root or merge commit (has </ul></div>
</dd>
</dl></div>
-<div class="para"><p>Finally, there is a fifth simplification mode available:</p></div>
-<div class="vlist"><dl>
-<dt>
+<div class="paragraph"><p>Finally, there is a fifth simplification mode available:</p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
--ancestry-path
</dt>
<dd>
@@ -1227,7 +1323,7 @@ If after this parent rewriting, <tt>C'</tt> is a root or merge commit (has range. I.e. only display commits that are ancestor of the "to"
commit, and descendants of the "from" commit.
</p>
-<div class="para"><p>As an example use case, consider the following commit history:</p></div>
+<div class="paragraph"><p>As an example use case, consider the following commit history:</p></div>
<div class="listingblock">
<div class="content">
<pre><tt> D---E-------F
@@ -1236,13 +1332,13 @@ If after this parent rewriting, <tt>C'</tt> is a root or merge commit (has / \
A-------K---------------L--M</tt></pre>
</div></div>
-<div class="para"><p>A regular <em>D..M</em> computes the set of commits that are ancestors of <tt>M</tt>,
+<div class="paragraph"><p>A regular <em>D..M</em> computes the set of commits that are ancestors of <tt>M</tt>,
but excludes the ones that are ancestors of <tt>D</tt>. This is useful to see
what happened to the history leading to <tt>M</tt> since <tt>D</tt>, in the sense
that "what does <tt>M</tt> have that did not exist in <tt>D</tt>". The result in this
example would be all the commits, except <tt>A</tt> and <tt>B</tt> (and <tt>D</tt> itself,
of course).</p></div>
-<div class="para"><p>When we want to find out what commits in <tt>M</tt> are contaminated with the
+<div class="paragraph"><p>When we want to find out what commits in <tt>M</tt> are contaminated with the
bug introduced by <tt>D</tt> and need fixing, however, we might want to view
only the subset of <em>D..M</em> that are actually descendants of <tt>D</tt>, i.e.
excluding <tt>C</tt> and <tt>K</tt>. This is exactly what the <em>--ancestry-path</em>
@@ -1257,7 +1353,7 @@ option does. Applied to the <em>D..M</em> range, it results in:</p></div> </div></div>
</dd>
</dl></div>
-<div class="para"><p>The <em>--simplify-by-decoration</em> option allows you to view only the
+<div class="paragraph"><p>The <em>--simplify-by-decoration</em> option allows you to view only the
big picture of the topology of the history, by omitting commits
that are not referenced by tags. Commits are marked as !TREESAME
(in other words, kept after history simplification rules described
@@ -1265,8 +1361,8 @@ above) if (1) they are referenced by tags, or (2) they change the contents of the paths given on the command line. All other
commits are marked as TREESAME (subject to be simplified away).</p></div>
<h3 id="_bisection_helpers">Bisection Helpers</h3><div style="clear:left"></div>
-<div class="vlist"><dl>
-<dt>
+<div class="dlist"><dl>
+<dt class="hdlist1">
--bisect
</dt>
<dd>
@@ -1284,25 +1380,25 @@ are no refs in <tt>refs/bisect/</tt>, if <div class="content">
<pre><tt> $ git rev-list --bisect foo ^bar ^baz</tt></pre>
</div></div>
-<div class="para"><p>outputs <em>midpoint</em>, the output of the two commands</p></div>
+<div class="paragraph"><p>outputs <em>midpoint</em>, the output of the two commands</p></div>
<div class="listingblock">
<div class="content">
<pre><tt> $ git rev-list foo ^midpoint
$ git rev-list midpoint ^bar ^baz</tt></pre>
</div></div>
-<div class="para"><p>would be of roughly the same length. Finding the change which
+<div class="paragraph"><p>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
+generate and test new 'midpoint’s until the commit chain is of length
one.</p></div>
-<div class="vlist"><dl>
-<dt>
+<div class="dlist"><dl>
+<dt class="hdlist1">
--bisect-vars
</dt>
<dd>
<p>
This calculates the same as <tt>--bisect</tt>, except that refs in
<tt>refs/bisect/</tt> are not used, and except that this outputs
-text ready to be eval'ed by the shell. These lines will assign the
+text ready to be eval’ed by the shell. These lines will assign the
name of the midpoint revision to the variable <tt>bisect_rev</tt>, and the
expected number of commits to be tested after <tt>bisect_rev</tt> is tested
to <tt>bisect_nr</tt>, the expected number of commits to be tested if
@@ -1312,7 +1408,7 @@ number of commits to be tested if <tt>bisect_rev</tt> turns out to be bad to <tt>bisect_all</tt>.
</p>
</dd>
-<dt>
+<dt class="hdlist1">
--bisect-all
</dt>
<dd>
@@ -1323,18 +1419,18 @@ commits. Refs in <tt>refs/bisect/</tt> are not used. The farthest from them is displayed first. (This is the only one displayed by
<tt>--bisect</tt>.)
</p>
-<div class="para"><p>This is useful because it makes it easy to choose a good commit to
+<div class="paragraph"><p>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).</p></div>
-<div class="para"><p>This option can be used along with <tt>--bisect-vars</tt>, in this case,
+<div class="paragraph"><p>This option can be used along with <tt>--bisect-vars</tt>, in this case,
after all the sorted commit objects, there will be the same text as if
<tt>--bisect-vars</tt> had been used alone.</p></div>
</dd>
</dl></div>
<h3 id="_commit_ordering">Commit Ordering</h3><div style="clear:left"></div>
-<div class="para"><p>By default, the commits are shown in reverse chronological order.</p></div>
-<div class="vlist"><dl>
-<dt>
+<div class="paragraph"><p>By default, the commits are shown in reverse chronological order.</p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
--topo-order
</dt>
<dd>
@@ -1343,7 +1439,7 @@ after all the sorted commit objects, there will be the same text as if descendant commits are shown before their parents).
</p>
</dd>
-<dt>
+<dt class="hdlist1">
--date-order
</dt>
<dd>
@@ -1353,7 +1449,7 @@ after all the sorted commit objects, there will be the same text as if are still ordered in the commit timestamp order.
</p>
</dd>
-<dt>
+<dt class="hdlist1">
--reverse
</dt>
<dd>
@@ -1364,9 +1460,9 @@ after all the sorted commit objects, there will be the same text as if </dd>
</dl></div>
<h3 id="_object_traversal">Object Traversal</h3><div style="clear:left"></div>
-<div class="para"><p>These options are mostly targeted for packing of git repositories.</p></div>
-<div class="vlist"><dl>
-<dt>
+<div class="paragraph"><p>These options are mostly targeted for packing of git repositories.</p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
--objects
</dt>
<dd>
@@ -1377,7 +1473,7 @@ after all the sorted commit objects, there will be the same text as if object <em>bar</em>, but not <em>foo</em>".
</p>
</dd>
-<dt>
+<dt class="hdlist1">
--objects-edge
</dt>
<dd>
@@ -1389,7 +1485,7 @@ after all the sorted commit objects, there will be the same text as if excluded commits to reduce network traffic.
</p>
</dd>
-<dt>
+<dt class="hdlist1">
--unpacked
</dt>
<dd>
@@ -1398,7 +1494,7 @@ after all the sorted commit objects, there will be the same text as if in packs.
</p>
</dd>
-<dt>
+<dt class="hdlist1">
--no-walk
</dt>
<dd>
@@ -1406,7 +1502,7 @@ after all the sorted commit objects, there will be the same text as if Only show the given revs, but do not traverse their ancestors.
</p>
</dd>
-<dt>
+<dt class="hdlist1">
--do-walk
</dt>
<dd>
@@ -1418,7 +1514,7 @@ after all the sorted commit objects, there will be the same text as if </div>
<h2 id="_pretty_formats">PRETTY FORMATS</h2>
<div class="sectionbody">
-<div class="para"><p>If the commit is a merge, and if the pretty-format
+<div class="paragraph"><p>If the commit is a merge, and if the pretty-format
is not <em>oneline</em>, <em>email</em> or <em>raw</em>, an additional line is
inserted before the <em>Author:</em> line. This line begins with
"Merge: " and the sha1s of ancestral commits are printed,
@@ -1427,13 +1523,13 @@ necessarily be the list of the <strong>direct</strong> parent commits if you have limited your view of history: for example, if you are
only interested in changes related to a certain directory or
file.</p></div>
-<div class="para"><p>There are several built-in formats, and you can define
+<div class="paragraph"><p>There are several built-in formats, and you can define
additional formats by setting a pretty.<name>
config option to either another format name, or a
<em>format:</em> string, as described below (see
<a href="git-config.html">git-config(1)</a>). Here are the details of the
built-in formats:</p></div>
-<div class="ilist"><ul>
+<div class="ulist"><ul>
<li>
<p>
<em>oneline</em>
@@ -1442,7 +1538,7 @@ built-in formats:</p></div> <div class="content">
<pre><tt><sha1> <title line></tt></pre>
</div></div>
-<div class="para"><p>This is designed to be as compact as possible.</p></div>
+<div class="paragraph"><p>This is designed to be as compact as possible.</p></div>
</li>
<li>
<p>
@@ -1537,7 +1633,7 @@ Subject: [PATCH] <title line></tt></pre> <p>
<em>raw</em>
</p>
-<div class="para"><p>The <em>raw</em> format shows the entire commit exactly as
+<div class="paragraph"><p>The <em>raw</em> format shows the entire commit exactly as
stored in the commit object. Notably, the SHA1s are
displayed in full, regardless of whether --abbrev or
--no-abbrev are used, and <em>parents</em> information show the
@@ -1548,20 +1644,19 @@ simplification into account.</p></div> <p>
<em>format:<string></em>
</p>
-<div class="para"><p>The <em>format:<string></em> format allows you to specify which information
+<div class="paragraph"><p>The <em>format:<string></em> format allows you to specify which information
you want to show. It works a little bit like printf format,
with the notable exception that you get a newline with <em>%n</em>
instead of <em>\n</em>.</p></div>
-<div class="para"><p>E.g, <em>format:"The author of %h was %an, %ar%nThe title was >>%s<<%n"</em>
+<div class="paragraph"><p>E.g, <em>format:"The author of %h was %an, %ar%nThe title was >>%s<<%n"</em>
would show something like this:</p></div>
<div class="listingblock">
<div class="content">
<pre><tt>The author of fe6e0ee was Junio C Hamano, 23 hours ago
-The title was >>t4119: test autocomputing -p<n> for traditional diff input.<<
-</tt></pre>
+The title was >>t4119: test autocomputing -p<n> for traditional diff input.<<</tt></pre>
</div></div>
-<div class="para"><p>The placeholders are:</p></div>
-<div class="ilist"><ul>
+<div class="paragraph"><p>The placeholders are:</p></div>
+<div class="ulist"><ul>
<li>
<p>
<em>%H</em>: commit hash
@@ -1798,21 +1893,21 @@ insert an empty string unless we are traversing reflog entries (e.g., by format if <tt>--decorate</tt> was not already provided on the command line.</td>
</tr></table>
</div>
-<div class="para"><p>If you add a <tt>+</tt> (plus sign) after <em>%</em> of a placeholder, a line-feed
+<div class="paragraph"><p>If you add a <tt>+</tt> (plus sign) after <em>%</em> of a placeholder, a line-feed
is inserted immediately before the expansion if and only if the
placeholder expands to a non-empty string.</p></div>
-<div class="para"><p>If you add a <tt>-</tt> (minus sign) after <em>%</em> of a placeholder, line-feeds that
+<div class="paragraph"><p>If you add a <tt>-</tt> (minus sign) after <em>%</em> of a placeholder, line-feeds that
immediately precede the expansion are deleted if and only if the
placeholder expands to an empty string.</p></div>
-<div class="para"><p>If you add a <tt> </tt> (space) after <em>%</em> of a placeholder, a space
+<div class="paragraph"><p>If you add a ` ` (space) after <em>%</em> of a placeholder, a space
is inserted immediately before the expansion if and only if the
placeholder expands to a non-empty string.</p></div>
-<div class="ilist"><ul>
+<div class="ulist"><ul>
<li>
<p>
<em>tformat:</em>
</p>
-<div class="para"><p>The <em>tformat:</em> format works exactly like <em>format:</em>, except that it
+<div class="paragraph"><p>The <em>tformat:</em> format works exactly like <em>format:</em>, except that it
provides "terminator" semantics instead of "separator" semantics. In
other words, each commit has the message terminator character (usually a
newline) appended, rather than a separator placed between entries.
@@ -1831,7 +1926,7 @@ $ git log -2 --pretty=tformat:%h 4da45bef \ 4da45be
7134973</tt></pre>
</div></div>
-<div class="para"><p>In addition, any unrecognized string that has a <tt>%</tt> in it is interpreted
+<div class="paragraph"><p>In addition, any unrecognized string that has a <tt>%</tt> in it is interpreted
as if it has <tt>tformat:</tt> in front of it. For example, these two are
equivalent:</p></div>
<div class="listingblock">
@@ -1844,20 +1939,20 @@ $ git log -2 --pretty=%h 4da45bef</tt></pre> </div>
<h2 id="_author">Author</h2>
<div class="sectionbody">
-<div class="para"><p>Written by Linus Torvalds <torvalds@osdl.org></p></div>
+<div class="paragraph"><p>Written by Linus Torvalds <<a href="mailto:torvalds@osdl.org">torvalds@osdl.org</a>></p></div>
</div>
<h2 id="_documentation">Documentation</h2>
<div class="sectionbody">
-<div class="para"><p>Documentation by David Greaves, Junio C Hamano, Jonas Fonseca
-and the git-list <git@vger.kernel.org>.</p></div>
+<div class="paragraph"><p>Documentation by David Greaves, Junio C Hamano, Jonas Fonseca
+and the git-list <<a href="mailto:git@vger.kernel.org">git@vger.kernel.org</a>>.</p></div>
</div>
<h2 id="_git">GIT</h2>
<div class="sectionbody">
-<div class="para"><p>Part of the <a href="git.html">git(1)</a> suite</p></div>
+<div class="paragraph"><p>Part of the <a href="git.html">git(1)</a> suite</p></div>
</div>
<div id="footer">
<div id="footer-text">
-Last updated 2010-10-22 04:11:10 UTC
+Last updated 2010-11-06 00:41:57 UTC
</div>
</div>
</body>
|