diff options
| author | Junio C Hamano <gitster@pobox.com> | 2014-01-17 14:46:49 -0800 |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2014-01-17 14:46:49 -0800 |
| commit | 61525f915b47e953b4288a9afcee45e47b352214 (patch) | |
| tree | f0649f89cc7a77c0296305f4673fc2bc7e0a6d54 /git-log.html | |
| parent | bc8d4783cac3c942fc9e8cf2f3eae4aea8cab5cb (diff) | |
| download | git-htmldocs-61525f915b47e953b4288a9afcee45e47b352214.tar.gz | |
Autogenerated HTML docs for v1.9-rc0
Diffstat (limited to 'git-log.html')
| -rw-r--r-- | git-log.html | 788 |
1 files changed, 396 insertions, 392 deletions
diff --git a/git-log.html b/git-log.html index 2662b153e..6bb8a43ed 100644 --- a/git-log.html +++ b/git-log.html @@ -3,7 +3,7 @@ <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head>
<meta http-equiv="Content-Type" content="application/xhtml+xml; charset=UTF-8" />
-<meta name="generator" content="AsciiDoc 8.6.8" />
+<meta name="generator" content="AsciiDoc 8.6.6" />
<title>git-log(1)</title>
<style type="text/css">
/* Shared CSS for AsciiDoc xhtml11 and html5 backends */
@@ -87,15 +87,11 @@ ul, ol, li > p { ul > li { color: #aaa; }
ul > li > * { color: black; }
-.monospaced, code, pre {
- font-family: "Courier New", Courier, monospace;
- font-size: inherit;
- color: navy;
+pre {
padding: 0;
margin: 0;
}
-
#author {
color: #527bbd;
font-weight: bold;
@@ -353,7 +349,7 @@ div.colist td img { margin-bottom: 0.1em;
}
-div.toclevel0, div.toclevel1, div.toclevel2, div.toclevel3, div.toclevel4 {
+div.toclevel1, div.toclevel2, div.toclevel3, div.toclevel4 {
margin-top: 0;
margin-bottom: 0;
}
@@ -411,14 +407,18 @@ span.underline { text-decoration: underline; } span.overline { text-decoration: overline; }
span.line-through { text-decoration: line-through; }
-div.unbreakable { page-break-inside: avoid; }
-
/*
* xhtml11 specific
*
* */
+tt {
+ font-family: monospace;
+ font-size: inherit;
+ color: navy;
+}
+
div.tableblock {
margin-top: 1.0em;
margin-bottom: 1.5em;
@@ -452,6 +452,12 @@ div.tableblock > table[frame="vsides"] { *
* */
+.monospaced {
+ font-family: monospace;
+ font-size: inherit;
+ color: navy;
+}
+
table.tableblock {
margin-top: 1.0em;
margin-bottom: 1.5em;
@@ -531,8 +537,6 @@ body.manpage div.sectionbody { @media print {
body.manpage div#toc { display: none; }
}
-
-
</style>
<script type="text/javascript">
/*<+'])');
+ var re = new RegExp('[hH]([2-'+(toclevels+1)+'])');
// Function that scans the DOM tree for header elements (the DOM2
// nodeIterator API would be a better technique but not supported by all
// browsers).
@@ -606,7 +610,7 @@ toc: function (toclevels) { var i;
for (i = 0; i < toc.childNodes.length; i++) {
var entry = toc.childNodes[i];
- if (entry.nodeName.toLowerCase() == 'div'
+ if (entry.nodeName == 'div'
&& entry.getAttribute("class")
&& entry.getAttribute("class").match(/^toclevel/))
tocEntriesToRemove.push(entry);
@@ -652,7 +656,7 @@ footnotes: function () { var entriesToRemove = [];
for (i = 0; i < noteholder.childNodes.length; i++) {
var entry = noteholder.childNodes[i];
- if (entry.nodeName.toLowerCase() == 'div' && entry.getAttribute("class") == "footnote")
+ if (entry.nodeName == 'div' && entry.getAttribute("class") == "footnote")
entriesToRemove.push(entry);
}
for (i = 0; i < entriesToRemove.length; i++) {
@@ -755,9 +759,9 @@ git-log(1) Manual Page <h2 id="_description">DESCRIPTION</h2>
<div class="sectionbody">
<div class="paragraph"><p>Shows the commit logs.</p></div>
-<div class="paragraph"><p>The command takes options applicable to the <code>git rev-list</code>
+<div class="paragraph"><p>The command takes options applicable to the <tt>git rev-list</tt>
command to control what is shown and how, and options applicable to
-the <code>git diff-*</code> commands to control how the changes
+the <tt>git diff-*</tt> commands to control how the changes
each commit introduces are shown.</p></div>
</div>
</div>
@@ -813,14 +817,14 @@ each commit introduces are shown.</p></div> </dt>
<dd>
<p>
- Without this flag, <code>git log -p <path>...</code> shows commits that
+ Without this flag, <tt>git log -p <path>...</tt> shows commits that
touch the specified paths, and diffs about the same specified
paths. With this, the full diff is shown for commits that touch
the specified paths; this means that "<path>…" limits only
commits, and doesn’t limit diff for those commits.
</p>
<div class="paragraph"><p>Note that this affects all diff-based output types, e.g. those
-produced by <code>--stat</code>, etc.</p></div>
+produced by <tt>--stat</tt>, etc.</p></div>
</dd>
<dt class="hdlist1">
--log-size
@@ -829,7 +833,7 @@ produced by <code>--stat</code>, etc.</p></div> <p>
Include a line “log size <number>” in the output for each commit,
where <number> is the length of that commit’s message in bytes.
- Intended to speed up tools that read log messages from <code>git log</code>
+ Intended to speed up tools that read log messages from <tt>git log</tt>
output by allowing them to allocate space in advance.
</p>
</dd>
@@ -863,7 +867,7 @@ absolute line number (lines count from 1).</p></div> </p>
<div class="paragraph"><p>This form will use the first line matching the given
POSIX regex. If <start> is a regex, it will search from the end of
-the previous <code>-L</code> range, if any, otherwise from the start of file.
+the previous <tt>-L</tt> range, if any, otherwise from the start of file.
If <start> is “^/regex/”, it will search from the start of file.
If <end> is a regex, it will search
starting at the line given by <start>.</p></div>
@@ -878,7 +882,7 @@ of lines before or after the line given by <start>.</p></div> </ul></div>
<div class="paragraph"><p>If “:<regex>” is given in place of <start> and <end>, it denotes the range
from the first funcname line that matches <regex>, up to the next
-funcname line. “:<regex>” searches from the end of the previous <code>-L</code> range,
+funcname line. “:<regex>” searches from the end of the previous <tt>-L</tt> range,
if any, otherwise from the start of file.
“^:<regex>” searches from the start of file.</p></div>
</dd>
@@ -888,10 +892,10 @@ if any, otherwise from the start of file. <dd>
<p>
Show only commits in the specified revision range. When no
- <revision range> is specified, it defaults to <code>HEAD</code> (i.e. the
- whole history leading to the current commit). <code>origin..HEAD</code>
+ <revision range> is specified, it defaults to <tt>HEAD</tt> (i.e. the
+ whole history leading to the current commit). <tt>origin..HEAD</tt>
specifies all the commits reachable from the current commit
- (i.e. <code>HEAD</code>), but not from <code>origin</code>. For a complete list of
+ (i.e. <tt>HEAD</tt>), but not from <tt>origin</tt>. For a complete list of
ways to spell <revision range>, see the <em>Specifying Ranges</em>
section of <a href="gitrevisions.html">gitrevisions(7)</a>.
</p>
@@ -916,11 +920,11 @@ options or the revision range, when confusion arises.</p></div> special notations explained in the description, additional commit
limiting may be applied.</p></div>
<div class="paragraph"><p>Using more options generally further limits the output (e.g.
-<code>--since=<date1></code> limits to commits newer than <code><date1></code>, and using it
-with <code>--grep=<pattern></code> further limits to commits whose log message
-has a line that matches <code><pattern></code>), unless otherwise noted.</p></div>
+<tt>--since=<date1></tt> limits to commits newer than <tt><date1></tt>, and using it
+with <tt>--grep=<pattern></tt> further limits to commits whose log message
+has a line that matches <tt><pattern></tt>), unless otherwise noted.</p></div>
<div class="paragraph"><p>Note that these are applied before commit
-ordering and formatting options, such as <code>--reverse</code>.</p></div>
+ordering and formatting options, such as <tt>--reverse</tt>.</p></div>
<div class="openblock">
<div class="content">
<div class="dlist"><dl>
@@ -978,9 +982,9 @@ ordering and formatting options, such as <code>--reverse</code>.</p></div> <p>
Limit the commits output to ones with author/committer
header lines that match the specified pattern (regular
- expression). With more than one <code>--author=<pattern></code>,
+ expression). With more than one <tt>--author=<pattern></tt>,
commits whose author matches any of the given patterns are
- chosen (similarly for multiple <code>--committer=<pattern></code>).
+ chosen (similarly for multiple <tt>--committer=<pattern></tt>).
</p>
</dd>
<dt class="hdlist1">
@@ -990,9 +994,9 @@ ordering and formatting options, such as <code>--reverse</code>.</p></div> <p>
Limit the commits output to ones with reflog entries that
match the specified pattern (regular expression). With
- more than one <code>--grep-reflog</code>, commits whose reflog message
+ more than one <tt>--grep-reflog</tt>, commits whose reflog message
matches any of the given patterns are chosen. It is an
- error to use this option unless <code>--walk-reflogs</code> is in use.
+ error to use this option unless <tt>--walk-reflogs</tt> is in use.
</p>
</dd>
<dt class="hdlist1">
@@ -1002,11 +1006,11 @@ ordering and formatting options, such as <code>--reverse</code>.</p></div> <p>
Limit the commits output to ones with log message that
matches the specified pattern (regular expression). With
- more than one <code>--grep=<pattern></code>, commits whose message
+ more than one <tt>--grep=<pattern></tt>, commits whose message
matches any of the given patterns are chosen (but see
- <code>--all-match</code>).
+ <tt>--all-match</tt>).
</p>
-<div class="paragraph"><p>When <code>--show-notes</code> is in effect, the message from the notes as
+<div class="paragraph"><p>When <tt>--show-notes</tt> is in effect, the message from the notes as
if it is part of the log message.</p></div>
</dd>
<dt class="hdlist1">
@@ -1014,7 +1018,7 @@ if it is part of the log message.</p></div> </dt>
<dd>
<p>
- Limit the commits output to ones that match all given <code>--grep</code>,
+ Limit the commits output to ones that match all given <tt>--grep</tt>,
instead of ones that match at least one.
</p>
</dd>
@@ -1085,7 +1089,7 @@ if it is part of the log message.</p></div> </dt>
<dd>
<p>
- Print only merge commits. This is exactly the same as <code>--min-parents=2</code>.
+ Print only merge commits. This is exactly the same as <tt>--min-parents=2</tt>.
</p>
</dd>
<dt class="hdlist1">
@@ -1094,7 +1098,7 @@ if it is part of the log message.</p></div> <dd>
<p>
Do not print commits with more than one parent. This is
- exactly the same as <code>--max-parents=1</code>.
+ exactly the same as <tt>--max-parents=1</tt>.
</p>
</dd>
<dt class="hdlist1">
@@ -1112,13 +1116,13 @@ if it is part of the log message.</p></div> <dd>
<p>
Show only commits which have at least (or at most) that many parent
- commits. In particular, <code>--max-parents=1</code> is the same as <code>--no-merges</code>,
- <code>--min-parents=2</code> is the same as <code>--merges</code>. <code>--max-parents=0</code>
- gives all root commits and <code>--min-parents=3</code> all octopus merges.
+ commits. In particular, <tt>--max-parents=1</tt> is the same as <tt>--no-merges</tt>,
+ <tt>--min-parents=2</tt> is the same as <tt>--merges</tt>. <tt>--max-parents=0</tt>
+ gives all root commits and <tt>--min-parents=3</tt> all octopus merges.
</p>
-<div class="paragraph"><p><code>--no-min-parents</code> and <code>--no-max-parents</code> reset these limits (to no limit)
-again. Equivalent forms are <code>--min-parents=0</code> (any commit has 0 or more
-parents) and <code>--max-parents=-1</code> (negative numbers denote no upper limit).</p></div>
+<div class="paragraph"><p><tt>--no-min-parents</tt> and <tt>--no-max-parents</tt> reset these limits (to no limit)
+again. Equivalent forms are <tt>--min-parents=0</tt> (any commit has 0 or more
+parents) and <tt>--max-parents=-1</tt> (negative numbers denote no upper limit).</p></div>
</dd>
<dt class="hdlist1">
--first-parent
@@ -1140,7 +1144,7 @@ parents) and <code>--max-parents=-1</code> (negative numbers denote no upper lim <dd>
<p>
Reverses the meaning of the <em>^</em> prefix (or lack thereof)
- for all following revision specifiers, up to the next <code>--not</code>.
+ for all following revision specifiers, up to the next <tt>--not</tt>.
</p>
</dd>
<dt class="hdlist1">
@@ -1148,7 +1152,7 @@ parents) and <code>--max-parents=-1</code> (negative numbers denote no upper lim </dt>
<dd>
<p>
- Pretend as if all the refs in <code>refs/</code> are listed on the
+ Pretend as if all the refs in <tt>refs/</tt> are listed on the
command line as <em><commit></em>.
</p>
</dd>
@@ -1157,7 +1161,7 @@ parents) and <code>--max-parents=-1</code> (negative numbers denote no upper lim </dt>
<dd>
<p>
- Pretend as if all the refs in <code>refs/heads</code> are listed
+ Pretend as if all the refs in <tt>refs/heads</tt> are listed
on the command line as <em><commit></em>. If <em><pattern></em> is given, limit
branches to ones matching given shell glob. If pattern lacks <em>?</em>,
<em>*</em>, or <em>[</em>, <em>/*</em> at the end is implied.
@@ -1168,7 +1172,7 @@ parents) and <code>--max-parents=-1</code> (negative numbers denote no upper lim </dt>
<dd>
<p>
- Pretend as if all the refs in <code>refs/tags</code> are listed
+ Pretend as if all the refs in <tt>refs/tags</tt> are listed
on the command line as <em><commit></em>. If <em><pattern></em> is given, limit
tags to ones matching given shell glob. If pattern lacks <em>?</em>, <em>*</em>,
or <em>[</em>, <em>/*</em> at the end is implied.
@@ -1179,7 +1183,7 @@ parents) and <code>--max-parents=-1</code> (negative numbers denote no upper lim </dt>
<dd>
<p>
- Pretend as if all the refs in <code>refs/remotes</code> are listed
+ Pretend as if all the refs in <tt>refs/remotes</tt> are listed
on the command line as <em><commit></em>. If <em><pattern></em> is given, limit
remote-tracking branches to ones matching given shell glob.
If pattern lacks <em>?</em>, <em>*</em>, or <em>[</em>, <em>/*</em> at the end is implied.
@@ -1201,17 +1205,17 @@ parents) and <code>--max-parents=-1</code> (negative numbers denote no upper lim </dt>
<dd>
<p>
- Do not include refs matching <em><glob-pattern></em> that the next <code>--all</code>,
- <code>--branches</code>, <code>--tags</code>, <code>--remotes</code>, or <code>--glob</code> would otherwise
+ Do not include refs matching <em><glob-pattern></em> that the next <tt>--all</tt>,
+ <tt>--branches</tt>, <tt>--tags</tt>, <tt>--remotes</tt>, or <tt>--glob</tt> would otherwise
consider. Repetitions of this option accumulate exclusion patterns
- up to the next <code>--all</code>, <code>--branches</code>, <code>--tags</code>, <code>--remotes</code>, or
- <code>--glob</code> option (other options or arguments do not clear
+ up to the next <tt>--all</tt>, <tt>--branches</tt>, <tt>--tags</tt>, <tt>--remotes</tt>, or
+ <tt>--glob</tt> option (other options or arguments do not clear
accumlated patterns).
</p>
-<div class="paragraph"><p>The patterns given should not begin with <code>refs/heads</code>, <code>refs/tags</code>, or
-<code>refs/remotes</code> when applied to <code>--branches</code>, <code>--tags</code>, or <code>--remotes</code>,
-respectively, and they must begin with <code>refs/</code> when applied to <code>--glob</code>
-or <code>--all</code>. If a trailing <em>/*</em> is intended, it must be given
+<div class="paragraph"><p>The patterns given should not begin with <tt>refs/heads</tt>, <tt>refs/tags</tt>, or
+<tt>refs/remotes</tt> when applied to <tt>--branches</tt>, <tt>--tags</tt>, or <tt>--remotes</tt>,
+respectively, and they must begin with <tt>refs/</tt> when applied to <tt>--glob</tt>
+or <tt>--all</tt>. If a trailing <em>/*</em> is intended, it must be given
explicitly.</p></div>
</dd>
<dt class="hdlist1">
@@ -1228,9 +1232,9 @@ explicitly.</p></div> </dt>
<dd>
<p>
- Pretend as if the bad bisection ref <code>refs/bisect/bad</code>
- was listed and as if it was followed by <code>--not</code> and the good
- bisection refs <code>refs/bisect/good-*</code> on the command
+ Pretend as if the bad bisection ref <tt>refs/bisect/bad</tt>
+ was listed and as if it was followed by <tt>--not</tt> and the good
+ bisection refs <tt>refs/bisect/good-*</tt> on the command
line.
</p>
</dd>
@@ -1250,8 +1254,8 @@ explicitly.</p></div> </dt>
<dd>
<p>
- Like <code>--cherry-pick</code> (see below) but mark equivalent commits
- with <code>=</code> rather than omitting them, and inequivalent ones with <code>+</code>.
+ Like <tt>--cherry-pick</tt> (see below) but mark equivalent commits
+ with <tt>=</tt> rather than omitting them, and inequivalent ones with <tt>+</tt>.
</p>
</dd>
<dt class="hdlist1">
@@ -1263,10 +1267,10 @@ explicitly.</p></div> another commit on the “other side” when the set of
commits are limited with symmetric difference.
</p>
-<div class="paragraph"><p>For example, if you have two branches, <code>A</code> and <code>B</code>, a usual way
+<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
-<code>--left-right</code> (see the example below in the description of
-the <code>--left-right</code> option). However, it shows the commits that were
+<tt>--left-right</tt> (see the example below in the description of
+the <tt>--left-right</tt> option). However, it 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></div>
@@ -1280,13 +1284,13 @@ excluded from the output.</p></div> <dd>
<p>
List only commits on the respective side of a symmetric range,
- i.e. only those which would be marked <code><</code> resp. <code>></code> by
- <code>--left-right</code>.
+ i.e. only those which would be marked <tt><</tt> resp. <tt>></tt> by
+ <tt>--left-right</tt>.
</p>
-<div class="paragraph"><p>For example, <code>--cherry-pick --right-only A...B</code> omits those
-commits from <code>B</code> which are in <code>A</code> or are patch-equivalent to a commit in
-<code>A</code>. In other words, this lists the <code>+</code> commits from <code>git cherry A B</code>.
-More precisely, <code>--cherry-pick --right-only --no-merges</code> gives the exact
+<div class="paragraph"><p>For example, <tt>--cherry-pick --right-only A...B</tt> omits those
+commits from <tt>B</tt> which are in <tt>A</tt> or are patch-equivalent to a commit in
+<tt>A</tt>. In other words, this lists the <tt>+</tt> commits from <tt>git cherry A B</tt>.
+More precisely, <tt>--cherry-pick --right-only --no-merges</tt> gives the exact
list.</p></div>
</dd>
<dt class="hdlist1">
@@ -1294,11 +1298,11 @@ list.</p></div> </dt>
<dd>
<p>
- A synonym for <code>--right-only --cherry-mark --no-merges</code>; useful to
+ A synonym for <tt>--right-only --cherry-mark --no-merges</tt>; useful to
limit the output to the commits on our side and mark those that
have been applied to the other side of a forked history with
- <code>git log --cherry upstream...mybranch</code>, similar to
- <code>git cherry upstream mybranch</code>.
+ <tt>git log --cherry upstream...mybranch</tt>, similar to
+ <tt>git cherry upstream mybranch</tt>.
</p>
</dd>
<dt class="hdlist1">
@@ -1315,14 +1319,14 @@ list.</p></div> exclude (that is, <em>^commit</em>, <em>commit1..commit2</em>,
nor <em>commit1...commit2</em> notations cannot be used).
</p>
-<div class="paragraph"><p>With <code>--pretty</code> format other than <code>oneline</code> (for obvious reasons),
+<div class="paragraph"><p>With <tt>--pretty</tt> format other than <tt>oneline</tt> (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
<em>commit@{now}</em>, output also uses <em>commit@{timestamp}</em> notation
-instead. Under <code>--pretty=oneline</code>, the commit message is
+instead. Under <tt>--pretty=oneline</tt>, the commit message is
prefixed with this information on the same line.
-This option cannot be combined with <code>--reverse</code>.
+This option cannot be combined with <tt>--reverse</tt>.
See also <a href="git-reflog.html">git-reflog(1)</a>.</p></div>
</dd>
<dt class="hdlist1">
@@ -1340,7 +1344,7 @@ See also <a href="git-reflog.html">git-reflog(1)</a>.</p></div> <dd>
<p>
Output excluded boundary commits. Boundary commits are
- prefixed with <code>-</code>.
+ prefixed with <tt>-</tt>.
</p>
</dd>
</dl></div>
@@ -1415,7 +1419,7 @@ Default mode </dt>
<dd>
<p>
- Additional option to <code>--full-history</code> to remove some needless
+ Additional option to <tt>--full-history</tt> to remove some needless
merges from the resulting history, as there are no selected
commits contributing to this merge.
</p>
@@ -1434,70 +1438,70 @@ Default mode </dd>
</dl></div>
<div class="paragraph"><p>A more detailed explanation follows.</p></div>
-<div class="paragraph"><p>Suppose you specified <code>foo</code> as the <paths>. We shall call commits
-that modify <code>foo</code> !TREESAME, and the rest TREESAME. (In a diff
-filtered for <code>foo</code>, they look different and equal, respectively.)</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="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 <code>foo</code> in this commit graph:</p></div>
+that you are filtering for a file <tt>foo</tt> in this commit graph:</p></div>
<div class="listingblock">
<div class="content">
-<pre><code> .-A---M---N---O---P---Q
+<pre><tt> .-A---M---N---O---P---Q
/ / / / / /
I B C D E Y
\ / / / / /
- `-------------' X</code></pre>
+ `-------------' X</tt></pre>
</div></div>
<div class="paragraph"><p>The horizontal line of history A---Q is taken to be the first parent of
each merge. The commits are:</p></div>
<div class="ulist"><ul>
<li>
<p>
-<code>I</code> is the initial commit, in which <code>foo</code> exists with contents
- “asdf”, and a file <code>quux</code> exists with contents “quux”. Initial
- commits are compared to an empty tree, so <code>I</code> is !TREESAME.
+<tt>I</tt> is the initial commit, in which <tt>foo</tt> exists with contents
+ “asdf”, and a file <tt>quux</tt> exists with contents “quux”. Initial
+ commits are compared to an empty tree, so <tt>I</tt> is !TREESAME.
</p>
</li>
<li>
<p>
-In <code>A</code>, <code>foo</code> contains just “foo”.
+In <tt>A</tt>, <tt>foo</tt> contains just “foo”.
</p>
</li>
<li>
<p>
-<code>B</code> contains the same change as <code>A</code>. Its merge <code>M</code> is trivial and
+<tt>B</tt> contains the same change as <tt>A</tt>. Its merge <tt>M</tt> is trivial and
hence TREESAME to all parents.
</p>
</li>
<li>
<p>
-<code>C</code> does not change <code>foo</code>, but its merge <code>N</code> changes it to “foobar”,
+<tt>C</tt> does not change <tt>foo</tt>, but its merge <tt>N</tt> changes it to “foobar”,
so it is not TREESAME to any parent.
</p>
</li>
<li>
<p>
-<code>D</code> sets <code>foo</code> to “baz”. Its merge <code>O</code> combines the strings from
- <code>N</code> and <code>D</code> to “foobarbaz”; i.e., it is not TREESAME to any parent.
+<tt>D</tt> sets <tt>foo</tt> to “baz”. Its merge <tt>O</tt> combines the strings from
+ <tt>N</tt> and <tt>D</tt> to “foobarbaz”; i.e., it is not TREESAME to any parent.
</p>
</li>
<li>
<p>
-<code>E</code> changes <code>quux</code> to “xyzzy”, and its merge <code>P</code> combines the
- strings to “quux xyzzy”. <code>P</code> is TREESAME to <code>O</code>, but not to <code>E</code>.
+<tt>E</tt> changes <tt>quux</tt> to “xyzzy”, and its merge <tt>P</tt> combines the
+ strings to “quux xyzzy”. <tt>P</tt> is TREESAME to <tt>O</tt>, but not to <tt>E</tt>.
</p>
</li>
<li>
<p>
-<code>X</code> is an independent root commit that added a new file <code>side</code>, and <code>Y</code>
- modified it. <code>Y</code> is TREESAME to <code>X</code>. Its merge <code>Q</code> added <code>side</code> to <code>P</code>, and
- <code>Q</code> is TREESAME to <code>P</code>, but not to <code>Y</code>.
+<tt>X</tt> is an independent root commit that added a new file <tt>side</tt>, and <tt>Y</tt>
+ modified it. <tt>Y</tt> is TREESAME to <tt>X</tt>. Its merge <tt>Q</tt> added <tt>side</tt> to <tt>P</tt>, and
+ <tt>Q</tt> is TREESAME to <tt>P</tt>, but not to <tt>Y</tt>.
</p>
</li>
</ul></div>
-<div class="paragraph"><p><code>rev-list</code> walks backwards through history, including or excluding
-commits based on whether <code>--full-history</code> and/or parent rewriting
-(via <code>--parents</code> or <code>--children</code>) are used. The following settings
+<div class="paragraph"><p><tt>rev-list</tt> walks backwards through history, including or excluding
+commits based on whether <tt>--full-history</tt> and/or parent rewriting
+(via <tt>--parents</tt> or <tt>--children</tt>) are used. The following settings
are available.</p></div>
<div class="dlist"><dl>
<dt class="hdlist1">
@@ -1506,7 +1510,7 @@ Default mode <dd>
<p>
Commits are included if they are not TREESAME to any parent
- (though this can be changed, see <code>--sparse</code> below). If the
+ (though this can be changed, see <tt>--sparse</tt> below). If the
commit was a merge, and it was TREESAME to one parent, follow
only that parent. (Even if there are several TREESAME
parents, follow only one of them.) Otherwise, follow all
@@ -1515,15 +1519,15 @@ Default mode <div class="paragraph"><p>This results in:</p></div>
<div class="listingblock">
<div class="content">
-<pre><code> .-A---N---O
+<pre><tt> .-A---N---O
/ / /
- I---------D</code></pre>
+ I---------D</tt></pre>
</div></div>
<div class="paragraph"><p>Note how the rule to only follow the TREESAME parent, if one is
-available, removed <code>B</code> from consideration entirely. <code>C</code> was
-considered via <code>N</code>, but is TREESAME. Root commits are compared to an
-empty tree, so <code>I</code> is !TREESAME.</p></div>
-<div class="paragraph"><p>Parent/child relations are only visible with <code>--parents</code>, but that does
+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="paragraph"><p>Parent/child relations are only visible with <tt>--parents</tt>, but that does
not affect the commits selected in default mode, so we have shown the
parent lines.</p></div>
</dd>
@@ -1540,10 +1544,10 @@ parent lines.</p></div> </p>
<div class="listingblock">
<div class="content">
-<pre><code> I A B N D O P Q</code></pre>
+<pre><tt> I A B N D O P Q</tt></pre>
</div></div>
-<div class="paragraph"><p><code>M</code> was excluded because it is TREESAME to both parents. <code>E</code>,
-<code>C</code> and <code>B</code> were all walked, but only <code>B</code> was !TREESAME, so the others
+<div class="paragraph"><p><tt>M</tt> was excluded because it is TREESAME to both parents. <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="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
@@ -1555,23 +1559,23 @@ them disconnected.</p></div> <dd>
<p>
Ordinary commits are only included if they are !TREESAME
- (though this can be changed, see <code>--sparse</code> below).
+ (though this can be changed, see <tt>--sparse</tt> below).
</p>
<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">
<div class="content">
-<pre><code> .-A---M---N---O---P---Q
+<pre><tt> .-A---M---N---O---P---Q
/ / / / /
I B / D /
\ / / / /
- `-------------'</code></pre>
+ `-------------'</tt></pre>
</div></div>
-<div class="paragraph"><p>Compare to <code>--full-history</code> without rewriting above. Note that <code>E</code>
+<div class="paragraph"><p>Compare to <tt>--full-history</tt> 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 <code>E</code>'s parent <code>I</code>. The same happened for <code>C</code> and
-<code>N</code>, and <code>X</code>, <code>Y</code> and <code>Q</code>.</p></div>
+rewritten to contain <tt>E</tt>'s parent <tt>I</tt>. The same happened for <tt>C</tt> and
+<tt>N</tt>, and <tt>X</tt>, <tt>Y</tt> and <tt>Q</tt>.</p></div>
</dd>
</dl></div>
<div class="paragraph"><p>In addition to the above settings, you can change whether TREESAME
@@ -1593,7 +1597,7 @@ affects inclusion:</p></div> <p>
All commits that are walked are included.
</p>
-<div class="paragraph"><p>Note that without <code>--full-history</code>, this still simplifies merges: if
+<div class="paragraph"><p>Note that without <tt>--full-history</tt>, 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>
@@ -1603,21 +1607,21 @@ sides of the merge are never walked.</p></div> <dd>
<p>
First, build a history graph in the same way that
- <code>--full-history</code> with parent rewriting does (see above).
+ <tt>--full-history</tt> with parent rewriting does (see above).
</p>
-<div class="paragraph"><p>Then simplify each commit <code>C</code> to its replacement <code>C'</code> in the final
+<div class="paragraph"><p>Then simplify each commit <tt>C</tt> to its replacement <tt>C'</tt> in the final
history according to the following rules:</p></div>
<div class="openblock">
<div class="content">
<div class="ulist"><ul>
<li>
<p>
-Set <code>C'</code> to <code>C</code>.
+Set <tt>C'</tt> to <tt>C</tt>.
</p>
</li>
<li>
<p>
-Replace each parent <code>P</code> of <code>C'</code> with its simplification <code>P'</code>. In
+Replace each parent <tt>P</tt> of <tt>C'</tt> with its simplification <tt>P'</tt>. In
the process, drop parents that are ancestors of other parents or that are
root commits TREESAME to an empty tree, and remove duplicates, but take care
to never drop all parents that we are TREESAME to.
@@ -1625,7 +1629,7 @@ Replace each parent <code>P</code> of <code>C'</code> with its simplification <c </li>
<li>
<p>
-If after this parent rewriting, <code>C'</code> is a root or merge commit (has
+If after this parent rewriting, <tt>C'</tt> 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>
@@ -1633,35 +1637,35 @@ If after this parent rewriting, <code>C'</code> is a root or merge commit (has </ul></div>
</div></div>
<div class="paragraph"><p>The effect of this is best shown by way of comparing to
-<code>--full-history</code> with parent rewriting. The example turns into:</p></div>
+<tt>--full-history</tt> with parent rewriting. The example turns into:</p></div>
<div class="listingblock">
<div class="content">
-<pre><code> .-A---M---N---O
+<pre><tt> .-A---M---N---O
/ / /
I B D
\ / /
- `---------'</code></pre>
+ `---------'</tt></pre>
</div></div>
-<div class="paragraph"><p>Note the major differences in <code>N</code>, <code>P</code>, and <code>Q</code> over <code>--full-history</code>:</p></div>
+<div class="paragraph"><p>Note the major differences in <tt>N</tt>, <tt>P</tt>, and <tt>Q</tt> over <tt>--full-history</tt>:</p></div>
<div class="openblock">
<div class="content">
<div class="ulist"><ul>
<li>
<p>
-<code>N</code>'s parent list had <code>I</code> removed, because it is an ancestor of the
- other parent <code>M</code>. Still, <code>N</code> remained because it is !TREESAME.
+<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.
</p>
</li>
<li>
<p>
-<code>P</code>'s parent list similarly had <code>I</code> removed. <code>P</code> was then
+<tt>P</tt>'s parent list similarly had <tt>I</tt> removed. <tt>P</tt> was then
removed completely, because it had one parent and is TREESAME.
</p>
</li>
<li>
<p>
-<code>Q</code>'s parent list had <code>Y</code> simplified to <code>X</code>. <code>X</code> was then removed, because it
- was a TREESAME root. <code>Q</code> was then removed completely, because it had one
+<tt>Q</tt>'s parent list had <tt>Y</tt> simplified to <tt>X</tt>. <tt>X</tt> was then removed, because it
+ was a TREESAME root. <tt>Q</tt> was then removed completely, because it had one
parent and is TREESAME.
</p>
</li>
@@ -1684,34 +1688,34 @@ If after this parent rewriting, <code>C'</code> is a root or merge commit (has <div class="paragraph"><p>As an example use case, consider the following commit history:</p></div>
<div class="listingblock">
<div class="content">
-<pre><code> D---E-------F
+<pre><tt> D---E-------F
/ \ \
B---C---G---H---I---J
/ \
- A-------K---------------L--M</code></pre>
+ A-------K---------------L--M</tt></pre>
</div></div>
-<div class="paragraph"><p>A regular <em>D..M</em> computes the set of commits that are ancestors of <code>M</code>,
-but excludes the ones that are ancestors of <code>D</code>. This is useful to see
-what happened to the history leading to <code>M</code> since <code>D</code>, in the sense
-that “what does <code>M</code> have that did not exist in <code>D</code>”. The result in this
-example would be all the commits, except <code>A</code> and <code>B</code> (and <code>D</code> itself,
+<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="paragraph"><p>When we want to find out what commits in <code>M</code> are contaminated with the
-bug introduced by <code>D</code> and need fixing, however, we might want to view
-only the subset of <em>D..M</em> that are actually descendants of <code>D</code>, i.e.
-excluding <code>C</code> and <code>K</code>. This is exactly what the <code>--ancestry-path</code>
+<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 <tt>--ancestry-path</tt>
option does. Applied to the <em>D..M</em> range, it results in:</p></div>
<div class="listingblock">
<div class="content">
-<pre><code> E-------F
+<pre><tt> E-------F
\ \
G---H---I---J
\
- L--M</code></pre>
+ L--M</tt></pre>
</div></div>
</dd>
</dl></div>
-<div class="paragraph"><p>The <code>--simplify-by-decoration</code> option allows you to view only the
+<div class="paragraph"><p>The <tt>--simplify-by-decoration</tt> 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
@@ -1753,14 +1757,14 @@ commits are marked as TREESAME (subject to be simplified away).</p></div> <div class="paragraph"><p>For example, in a commit history like this:</p></div>
<div class="listingblock">
<div class="content">
-<pre><code> ---1----2----4----7
+<pre><tt> ---1----2----4----7
\ \
- 3----5----6----8---</code></pre>
+ 3----5----6----8---</tt></pre>
</div></div>
-<div class="paragraph"><p>where the numbers denote the order of commit timestamps, <code>git
-rev-list</code> and friends with <code>--date-order</code> show the commits in the
+<div class="paragraph"><p>where the numbers denote the order of commit timestamps, <tt>git
+rev-list</tt> and friends with <tt>--date-order</tt> show the commits in the
timestamp order: 8 7 6 5 4 3 2 1.</p></div>
-<div class="paragraph"><p>With <code>--topo-order</code>, they would show 8 6 5 3 7 4 2 1 (or 8 7 4 2 6 5
+<div class="paragraph"><p>With <tt>--topo-order</tt>, they would show 8 6 5 3 7 4 2 1 (or 8 7 4 2 6 5
3 1); some older commits are shown before newer ones in order to
avoid showing the commits from two parallel development track mixed
together.</p></div>
@@ -1771,7 +1775,7 @@ together.</p></div> <dd>
<p>
Output the commits in reverse order.
- Cannot be combined with <code>--walk-reflogs</code>.
+ Cannot be combined with <tt>--walk-reflogs</tt>.
</p>
</dd>
</dl></div>
@@ -1786,7 +1790,7 @@ together.</p></div> <dd>
<p>
Print the object IDs of any object referenced by the listed
- commits. <code>--objects foo ^bar</code> thus means “send me
+ commits. <tt>--objects foo ^bar</tt> thus means “send me
all object IDs which I need to download if I have the commit
object <em>bar</em> but not <em>foo</em>”.
</p>
@@ -1796,7 +1800,7 @@ together.</p></div> </dt>
<dd>
<p>
- Similar to <code>--objects</code>, but also print the IDs of excluded
+ Similar to <tt>--objects</tt>, but also print the IDs of excluded
commits prefixed with a “-” character. This is used by
<a href="git-pack-objects.html">git-pack-objects(1)</a> to build “thin” pack, which records
objects in deltified form based on objects contained in these
@@ -1808,7 +1812,7 @@ together.</p></div> </dt>
<dd>
<p>
- Only useful with <code>--objects</code>; print the object IDs that are not
+ Only useful with <tt>--objects</tt>; print the object IDs that are not
in packs.
</p>
</dd>
@@ -1819,8 +1823,8 @@ together.</p></div> <p>
Only show the given commits, but do not traverse their ancestors.
This has no effect if a range is specified. If the argument
- <code>unsorted</code> is given, the commits are shown in the order they were
- given on the command line. Otherwise (if <code>sorted</code> or no argument
+ <tt>unsorted</tt> is given, the commits are shown in the order they were
+ given on the command line. Otherwise (if <tt>sorted</tt> or no argument
was given), the commits are shown in reverse chronological order
by commit time.
</p>
@@ -1830,7 +1834,7 @@ together.</p></div> </dt>
<dd>
<p>
- Overrides a previous <code>--no-walk</code>.
+ Overrides a previous <tt>--no-walk</tt>.
</p>
</dd>
</dl></div>
@@ -1874,7 +1878,7 @@ people using 80-column terminals.</p></div> <dd>
<p>
Show the full 40-byte hexadecimal commit object name. This negates
- <code>--abbrev-commit</code> and those options which imply it such as
+ <tt>--abbrev-commit</tt> and those options which imply it such as
"--oneline". It also overrides the <em>log.abbrevCommit</em> variable.
</p>
</dd>
@@ -1906,15 +1910,15 @@ people using 80-column terminals.</p></div> <p>
Show the notes (see <a href="git-notes.html">git-notes(1)</a>) that annotate the
commit, when showing the commit log message. This is the default
- for <code>git log</code>, <code>git show</code> and <code>git whatchanged</code> commands when
- there is no <code>--pretty</code>, <code>--format</code> nor <code>--oneline</code> option given
+ for <tt>git log</tt>, <tt>git show</tt> and <tt>git whatchanged</tt> commands when
+ there is no <tt>--pretty</tt>, <tt>--format</tt> nor <tt>--oneline</tt> option given
on the command line.
</p>
<div class="paragraph"><p>By default, the notes shown are from the notes refs listed in the
<em>core.notesRef</em> and <em>notes.displayRef</em> variables (or corresponding
environment overrides). See <a href="git-config.html">git-config(1)</a> for more details.</p></div>
<div class="paragraph"><p>With an optional <em><ref></em> argument, show this notes ref instead of the
-default notes ref(s). The ref is taken to be in <code>refs/notes/</code> if it
+default notes ref(s). The ref is taken to be in <tt>refs/notes/</tt> if it
is not qualified.</p></div>
<div class="paragraph"><p>Multiple --notes options can be combined to control which notes are
being displayed. Examples: "--notes=foo" will show only notes from
@@ -1926,7 +1930,7 @@ being displayed. Examples: "--notes=foo" will show only notes from </dt>
<dd>
<p>
- Do not show notes. This negates the above <code>--notes</code> option, by
+ Do not show notes. This negates the above <tt>--notes</tt> option, by
resetting the list of notes refs from which notes are shown.
Options are parsed in the order given on the command line, so e.g.
"--notes --notes=foo --no-notes --notes=bar" will only show notes
@@ -1951,7 +1955,7 @@ being displayed. Examples: "--notes=foo" will show only notes from <dd>
<p>
Check the validity of a signed commit object by passing the signature
- to <code>gpg --verify</code> and show the output.
+ to <tt>gpg --verify</tt> and show the output.
</p>
</dd>
<dt class="hdlist1">
@@ -1959,7 +1963,7 @@ being displayed. Examples: "--notes=foo" will show only notes from </dt>
<dd>
<p>
- Synonym for <code>--date=relative</code>.
+ Synonym for <tt>--date=relative</tt>.
</p>
</dd>
<dt class="hdlist1">
@@ -1968,18 +1972,18 @@ being displayed. Examples: "--notes=foo" will show only notes from <dd>
<p>
Only takes effect for dates shown in human-readable format, such
- as when using <code>--pretty</code>. <code>log.date</code> config variable sets a default
- value for the log command’s <code>--date</code> option.
+ as when using <tt>--pretty</tt>. <tt>log.date</tt> config variable sets a default
+ value for the log command’s <tt>--date</tt> option.
</p>
-<div class="paragraph"><p><code>--date=relative</code> 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="paragraph"><p><code>--date=local</code> shows timestamps in user’s local time zone.</p></div>
-<div class="paragraph"><p><code>--date=iso</code> (or <code>--date=iso8601</code>) shows timestamps in ISO 8601 format.</p></div>
-<div class="paragraph"><p><code>--date=rfc</code> (or <code>--date=rfc2822</code>) shows timestamps in RFC 2822
+<div class="paragraph"><p><tt>--date=local</tt> shows timestamps in user’s local time zone.</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 email messages.</p></div>
-<div class="paragraph"><p><code>--date=short</code> shows only the date, but not the time, in <code>YYYY-MM-DD</code> format.</p></div>
-<div class="paragraph"><p><code>--date=raw</code> shows the date in the internal raw Git format <code>%s %z</code> format.</p></div>
-<div class="paragraph"><p><code>--date=default</code> shows timestamps in the original time zone
+<div class="paragraph"><p><tt>--date=short</tt> shows only the date, but not the 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 time zone
(either committer’s or author’s).</p></div>
</dd>
<dt class="hdlist1">
@@ -2006,30 +2010,30 @@ format, often found in email messages.</p></div> <dd>
<p>
Mark which side of a symmetric diff a commit is reachable from.
- Commits from the left side are prefixed with <code><</code> and those from
- the right with <code>></code>. If combined with <code>--boundary</code>, those
- commits are prefixed with <code>-</code>.
+ Commits from the left side are prefixed with <tt><</tt> and those from
+ the right with <tt>></tt>. If combined with <tt>--boundary</tt>, those
+ commits are prefixed with <tt>-</tt>.
</p>
<div class="paragraph"><p>For example, if you have this topology:</p></div>
<div class="listingblock">
<div class="content">
-<pre><code> y---b---b branch B
+<pre><tt> y---b---b branch B
/ \ /
/ .
/ / \
- o---x---a---a branch A</code></pre>
+ o---x---a---a branch A</tt></pre>
</div></div>
<div class="paragraph"><p>you would get an output like this:</p></div>
<div class="listingblock">
<div class="content">
-<pre><code> $ git rev-list --left-right --boundary --pretty=oneline A...B
+<pre><tt> $ 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</code></pre>
+ -xxxxxxx... 1st on a</tt></pre>
</div></div>
</dd>
<dt class="hdlist1">
@@ -2043,8 +2047,8 @@ format, often found in email messages.</p></div> to be drawn properly.
</p>
<div class="paragraph"><p>This enables parent rewriting, see <em>History Simplification</em> below.</p></div>
-<div class="paragraph"><p>This implies the <code>--topo-order</code> option by default, but the
-<code>--date-order</code> option may also be specified.</p></div>
+<div class="paragraph"><p>This implies the <tt>--topo-order</tt> option by default, but the
+<tt>--date-order</tt> option may also be specified.</p></div>
</dd>
</dl></div>
</div>
@@ -2071,7 +2075,7 @@ options may be given. See <a href="git-diff-files.html">git-diff-files(1)</a> fo </dt>
<dd>
<p>
- This flag implies the <code>-c</code> option and further compresses the
+ This flag implies the <tt>-c</tt> option and further compresses the
patch output by omitting uninteresting hunks whose contents in
the parents have only two variants and the merge result picks
one of them without modification.
@@ -2085,7 +2089,7 @@ options may be given. See <a href="git-diff-files.html">git-diff-files(1)</a> fo This flag makes the merge commits show the full diff like
regular commits; for each merge parent, a separate log entry
and diff is generated. An exception is that only diff against
- the first parent is shown when <code>--first-parent</code> option is given;
+ the first parent is shown when <tt>--first-parent</tt> option is given;
in that case, the output represents the changes the merge
brought <em>into</em> the then-current branch.
</p>
@@ -2103,7 +2107,7 @@ options may be given. See <a href="git-diff-files.html">git-diff-files(1)</a> fo </dt>
<dd>
<p>
- Show the tree objects in the diff output. This implies <code>-r</code>.
+ Show the tree objects in the diff output. This implies <tt>-r</tt>.
</p>
</dd>
</dl></div>
@@ -2135,7 +2139,7 @@ built-in formats:</p></div> </p>
<div class="literalblock">
<div class="content">
-<pre><code><sha1> <title line></code></pre>
+<pre><tt><sha1> <title line></tt></pre>
</div></div>
<div class="paragraph"><p>This is designed to be as compact as possible.</p></div>
</li>
@@ -2145,12 +2149,12 @@ built-in formats:</p></div> </p>
<div class="literalblock">
<div class="content">
-<pre><code>commit <sha1>
-Author: <author></code></pre>
+<pre><tt>commit <sha1>
+Author: <author></tt></pre>
</div></div>
<div class="literalblock">
<div class="content">
-<pre><code><title line></code></pre>
+<pre><tt><title line></tt></pre>
</div></div>
</li>
<li>
@@ -2159,17 +2163,17 @@ Author: <author></code></pre> </p>
<div class="literalblock">
<div class="content">
-<pre><code>commit <sha1>
+<pre><tt>commit <sha1>
Author: <author>
-Date: <author date></code></pre>
+Date: <author date></tt></pre>
</div></div>
<div class="literalblock">
<div class="content">
-<pre><code><title line></code></pre>
+<pre><tt><title line></tt></pre>
</div></div>
<div class="literalblock">
<div class="content">
-<pre><code><full commit message></code></pre>
+<pre><tt><full commit message></tt></pre>
</div></div>
</li>
<li>
@@ -2178,17 +2182,17 @@ Date: <author date></code></pre> </p>
<div class="literalblock">
<div class="content">
-<pre><code>commit <sha1>
+<pre><tt>commit <sha1>
Author: <author>
-Commit: <committer></code></pre>
+Commit: <committer></tt></pre>
</div></div>
<div class="literalblock">
<div class="content">
-<pre><code><title line></code></pre>
+<pre><tt><title line></tt></pre>
</div></div>
<div class="literalblock">
<div class="content">
-<pre><code><full commit message></code></pre>
+<pre><tt><full commit message></tt></pre>
</div></div>
</li>
<li>
@@ -2197,19 +2201,19 @@ Commit: <committer></code></pre> </p>
<div class="literalblock">
<div class="content">
-<pre><code>commit <sha1>
+<pre><tt>commit <sha1>
Author: <author>
AuthorDate: <author date>
Commit: <committer>
-CommitDate: <committer date></code></pre>
+CommitDate: <committer date></tt></pre>
</div></div>
<div class="literalblock">
<div class="content">
-<pre><code><title line></code></pre>
+<pre><tt><title line></tt></pre>
</div></div>
<div class="literalblock">
<div class="content">
-<pre><code><full commit message></code></pre>
+<pre><tt><full commit message></tt></pre>
</div></div>
</li>
<li>
@@ -2218,14 +2222,14 @@ CommitDate: <committer date></code></pre> </p>
<div class="literalblock">
<div class="content">
-<pre><code>From <sha1> <date>
+<pre><tt>From <sha1> <date>
From: <author>
Date: <author date>
-Subject: [PATCH] <title line></code></pre>
+Subject: [PATCH] <title line></tt></pre>
</div></div>
<div class="literalblock">
<div class="content">
-<pre><code><full commit message></code></pre>
+<pre><tt><full commit message></tt></pre>
</div></div>
</li>
<li>
@@ -2251,8 +2255,8 @@ instead of <em>\n</em>.</p></div> would show something like this:</p></div>
<div class="listingblock">
<div class="content">
-<pre><code>The author of fe6e0ee was Junio C Hamano, 23 hours ago
-The title was >>t4119: test autocomputing -p<n> for traditional diff input.<<</code></pre>
+<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>
</div></div>
<div class="paragraph"><p>The placeholders are:</p></div>
<div class="ulist"><ul>
@@ -2438,12 +2442,12 @@ The title was >>t4119: test autocomputing -p<n> for traditional diff </li>
<li>
<p>
-<em>%gD</em>: reflog selector, e.g., <code>refs/stash@{1}</code>
+<em>%gD</em>: reflog selector, e.g., <tt>refs/stash@{1}</tt>
</p>
</li>
<li>
<p>
-<em>%gd</em>: shortened reflog selector, e.g., <code>stash@{1}</code>
+<em>%gd</em>: shortened reflog selector, e.g., <tt>stash@{1}</tt>
</p>
</li>
<li>
@@ -2496,10 +2500,10 @@ The title was >>t4119: test autocomputing -p<n> for traditional diff <li>
<p>
<em>%C(…)</em>: color specification, as described in color.branch.* config option;
- adding <code>auto,</code> at the beginning will emit color only when colors are
- enabled for log output (by <code>color.diff</code>, <code>color.ui</code>, or <code>--color</code>, and
- respecting the <code>auto</code> settings of the former if we are going to a
- terminal). <code>auto</code> alone (i.e. <code>%C(auto)</code>) will turn on auto coloring
+ adding <tt>auto,</tt> at the beginning will emit color only when colors are
+ enabled for log output (by <tt>color.diff</tt>, <tt>color.ui</tt>, or <tt>--color</tt>, and
+ respecting the <tt>auto</tt> settings of the former if we are going to a
+ terminal). <tt>auto</tt> alone (i.e. <tt>%C(auto)</tt>) will turn on auto coloring
on the next placeholders until the color is switched again.
</p>
</li>
@@ -2572,16 +2576,16 @@ The title was >>t4119: test autocomputing -p<n> for traditional diff <div class="title">Note</div>
</td>
<td class="content">Some placeholders may depend on other options given to the
-revision traversal engine. For example, the <code>%g*</code> reflog options will
+revision traversal engine. For example, the <tt>%g*</tt> reflog options will
insert an empty string unless we are traversing reflog entries (e.g., by
-<code>git log -g</code>). The <code>%d</code> placeholder will use the "short" decoration
-format if <code>--decorate</code> was not already provided on the command line.</td>
+<tt>git log -g</tt>). The <tt>%d</tt> placeholder will use the "short" decoration
+format if <tt>--decorate</tt> was not already provided on the command line.</td>
</tr></table>
</div>
-<div class="paragraph"><p>If you add a <code>+</code> (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="paragraph"><p>If you add a <code>-</code> (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="paragraph"><p>If you add a ` ` (space) after <em>%</em> of a placeholder, a space
@@ -2601,7 +2605,7 @@ terminated with a new line, just as the "oneline" format does. For example:</p></div>
<div class="listingblock">
<div class="content">
-<pre><code>$ git log -2 --pretty=format:%h 4da45bef \
+<pre><tt>$ git log -2 --pretty=format:%h 4da45bef \
| perl -pe '$_ .= " -- NO NEWLINE\n" unless /\n/'
4da45be
7134973 -- NO NEWLINE
@@ -2609,15 +2613,15 @@ For example:</p></div> $ git log -2 --pretty=tformat:%h 4da45bef \
| perl -pe '$_ .= " -- NO NEWLINE\n" unless /\n/'
4da45be
-7134973</code></pre>
+7134973</tt></pre>
</div></div>
-<div class="paragraph"><p>In addition, any unrecognized string that has a <code>%</code> in it is interpreted
-as if it has <code>tformat:</code> in front of it. For example, these two are
+<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">
<div class="content">
-<pre><code>$ git log -2 --pretty=tformat:%h 4da45bef
-$ git log -2 --pretty=%h 4da45bef</code></pre>
+<pre><tt>$ git log -2 --pretty=tformat:%h 4da45bef
+$ git log -2 --pretty=%h 4da45bef</tt></pre>
</div></div>
</li>
</ul></div>
@@ -2650,8 +2654,8 @@ $ git log -2 --pretty=%h 4da45bef</code></pre> </dt>
<dd>
<p>
- Suppress diff output. Useful for commands like <code>git show</code> that
- show the patch by default, or to cancel the effect of <code>--patch</code>.
+ Suppress diff output. Useful for commands like <tt>git show</tt> that
+ show the patch by default, or to cancel the effect of <tt>--patch</tt>.
</p>
</dd>
<dt class="hdlist1">
@@ -2664,7 +2668,7 @@ $ git log -2 --pretty=%h 4da45bef</code></pre> <p>
Generate diffs with <n> lines of context instead of
the usual three.
- Implies <code>-p</code>.
+ Implies <tt>-p</tt>.
</p>
</dd>
<dt class="hdlist1">
@@ -2681,7 +2685,7 @@ $ git log -2 --pretty=%h 4da45bef</code></pre> </dt>
<dd>
<p>
- Synonym for <code>-p --raw</code>.
+ Synonym for <tt>-p --raw</tt>.
</p>
</dd>
<dt class="hdlist1">
@@ -2720,7 +2724,7 @@ $ git log -2 --pretty=%h 4da45bef</code></pre> <div class="content">
<div class="dlist"><dl>
<dt class="hdlist1">
-<code>default</code>, <code>myers</code>
+<tt>default</tt>, <tt>myers</tt>
</dt>
<dd>
<p>
@@ -2728,7 +2732,7 @@ $ git log -2 --pretty=%h 4da45bef</code></pre> </p>
</dd>
<dt class="hdlist1">
-<code>minimal</code>
+<tt>minimal</tt>
</dt>
<dd>
<p>
@@ -2737,7 +2741,7 @@ $ git log -2 --pretty=%h 4da45bef</code></pre> </p>
</dd>
<dt class="hdlist1">
-<code>patience</code>
+<tt>patience</tt>
</dt>
<dd>
<p>
@@ -2745,7 +2749,7 @@ $ git log -2 --pretty=%h 4da45bef</code></pre> </p>
</dd>
<dt class="hdlist1">
-<code>histogram</code>
+<tt>histogram</tt>
</dt>
<dd>
<p>
@@ -2757,7 +2761,7 @@ $ git log -2 --pretty=%h 4da45bef</code></pre> </div></div>
<div class="paragraph"><p>For instance, if you configured diff.algorithm variable to a
non-default value and want to use the default one, then you
-have to use <code>--diff-algorithm=default</code> option.</p></div>
+have to use <tt>--diff-algorithm=default</tt> option.</p></div>
</dd>
<dt class="hdlist1">
--stat[=<width>[,<name-width>[,<count>]]]
@@ -2768,29 +2772,29 @@ have to use <code>--diff-algorithm=default</code> option.</p></div> will be used for the filename part, and the rest for the graph
part. Maximum width defaults to terminal width, or 80 columns
if not connected to a terminal, and can be overridden by
- <code><width></code>. The width of the filename part can be limited by
- giving another width <code><name-width></code> after a comma. The width
+ <tt><width></tt>. The width of the filename part can be limited by
+ giving another width <tt><name-width></tt> after a comma. The width
of the graph part can be limited by using
- <code>--stat-graph-width=<width></code> (affects all commands generating
- a stat graph) or by setting <code>diff.statGraphWidth=<width></code>
- (does not affect <code>git format-patch</code>).
- By giving a third parameter <code><count></code>, you can limit the
- output to the first <code><count></code> lines, followed by <code>...</code> if
+ <tt>--stat-graph-width=<width></tt> (affects all commands generating
+ a stat graph) or by setting <tt>diff.statGraphWidth=<width></tt>
+ (does not affect <tt>git format-patch</tt>).
+ By giving a third parameter <tt><count></tt>, you can limit the
+ output to the first <tt><count></tt> lines, followed by <tt>...</tt> if
there are more.
</p>
-<div class="paragraph"><p>These parameters can also be set individually with <code>--stat-width=<width></code>,
-<code>--stat-name-width=<name-width></code> and <code>--stat-count=<count></code>.</p></div>
+<div class="paragraph"><p>These parameters can also be set individually with <tt>--stat-width=<width></tt>,
+<tt>--stat-name-width=<name-width></tt> and <tt>--stat-count=<count></tt>.</p></div>
</dd>
<dt class="hdlist1">
--numstat
</dt>
<dd>
<p>
- Similar to <code>--stat</code>, but shows number of added and
+ Similar to <tt>--stat</tt>, but shows number of added and
deleted lines in decimal notation and pathname without
abbreviation, to make it more machine friendly. For
- binary files, outputs two <code>-</code> instead of saying
- <code>0 0</code>.
+ binary files, outputs two <tt>-</tt> instead of saying
+ <tt>0 0</tt>.
</p>
</dd>
<dt class="hdlist1">
@@ -2798,7 +2802,7 @@ have to use <code>--diff-algorithm=default</code> option.</p></div> </dt>
<dd>
<p>
- Output only the last line of the <code>--stat</code> format containing total
+ Output only the last line of the <tt>--stat</tt> format containing total
number of modified files, as well as number of added and deleted
lines.
</p>
@@ -2809,9 +2813,9 @@ have to use <code>--diff-algorithm=default</code> option.</p></div> <dd>
<p>
Output the distribution of relative amount of changes for each
- sub-directory. The behavior of <code>--dirstat</code> can be customized by
+ sub-directory. The behavior of <tt>--dirstat</tt> can be customized by
passing it a comma separated list of parameters.
- The defaults are controlled by the <code>diff.dirstat</code> configuration
+ The defaults are controlled by the <tt>diff.dirstat</tt> configuration
variable (see <a href="git-config.html">git-config(1)</a>).
The following parameters are available:
</p>
@@ -2819,7 +2823,7 @@ have to use <code>--diff-algorithm=default</code> option.</p></div> <div class="content">
<div class="dlist"><dl>
<dt class="hdlist1">
-<code>changes</code>
+<tt>changes</tt>
</dt>
<dd>
<p>
@@ -2831,39 +2835,39 @@ have to use <code>--diff-algorithm=default</code> option.</p></div> </p>
</dd>
<dt class="hdlist1">
-<code>lines</code>
+<tt>lines</tt>
</dt>
<dd>
<p>
Compute the dirstat numbers by doing the regular line-based diff
analysis, and summing the removed/added line counts. (For binary
files, count 64-byte chunks instead, since binary files have no
- natural concept of lines). This is a more expensive <code>--dirstat</code>
- behavior than the <code>changes</code> behavior, but it does count rearranged
+ natural concept of lines). This is a more expensive <tt>--dirstat</tt>
+ behavior than the <tt>changes</tt> behavior, but it does count rearranged
lines within a file as much as other changes. The resulting output
- is consistent with what you get from the other <code>--*stat</code> options.
+ is consistent with what you get from the other <tt>--*stat</tt> options.
</p>
</dd>
<dt class="hdlist1">
-<code>files</code>
+<tt>files</tt>
</dt>
<dd>
<p>
Compute the dirstat numbers by counting the number of files changed.
Each changed file counts equally in the dirstat analysis. This is
- the computationally cheapest <code>--dirstat</code> behavior, since it does
+ the computationally cheapest <tt>--dirstat</tt> behavior, since it does
not have to look at the file contents at all.
</p>
</dd>
<dt class="hdlist1">
-<code>cumulative</code>
+<tt>cumulative</tt>
</dt>
<dd>
<p>
Count changes in a child directory for the parent directory as well.
- Note that when using <code>cumulative</code>, the sum of the percentages
+ Note that when using <tt>cumulative</tt>, the sum of the percentages
reported may exceed 100%. The default (non-cumulative) behavior can
- be specified with the <code>noncumulative</code> parameter.
+ be specified with the <tt>noncumulative</tt> parameter.
</p>
</dd>
<dt class="hdlist1">
@@ -2881,7 +2885,7 @@ have to use <code>--diff-algorithm=default</code> option.</p></div> <div class="paragraph"><p>Example: The following will count changed files, while ignoring
directories with less than 10% of the total amount of changed files,
and accumulating child directory counts in the parent directories:
-<code>--dirstat=files,10,cumulative</code>.</p></div>
+<tt>--dirstat=files,10,cumulative</tt>.</p></div>
</dd>
<dt class="hdlist1">
--summary
@@ -2897,7 +2901,7 @@ and accumulating child directory counts in the parent directories: </dt>
<dd>
<p>
- Synonym for <code>-p --stat</code>.
+ Synonym for <tt>-p --stat</tt>.
</p>
</dd>
<dt class="hdlist1">
@@ -2907,10 +2911,10 @@ and accumulating child directory counts in the parent directories: <p>
Separate the commits with NULs instead of with new newlines.
</p>
-<div class="paragraph"><p>Also, when <code>--raw</code> or <code>--numstat</code> has been given, do not munge
+<div class="paragraph"><p>Also, when <tt>--raw</tt> or <tt>--numstat</tt> has been given, do not munge
pathnames and use NULs as output field terminators.</p></div>
<div class="paragraph"><p>Without this option, each pathname output will have TAB, LF, double quotes,
-and backslash characters replaced with <code>\t</code>, <code>\n</code>, <code>\"</code>, and <code>\\</code>,
+and backslash characters replaced with <tt>\t</tt>, <tt>\n</tt>, <tt>\"</tt>, and <tt>\\</tt>,
respectively, and the pathname will be enclosed in double quotes if
any of those replacements occurred.</p></div>
</dd>
@@ -2928,7 +2932,7 @@ any of those replacements occurred.</p></div> <dd>
<p>
Show only names and status of changed files. See the description
- of the <code>--diff-filter</code> option on what the status letters mean.
+ of the <tt>--diff-filter</tt> option on what the status letters mean.
</p>
</dd>
<dt class="hdlist1">
@@ -2936,13 +2940,13 @@ any of those replacements occurred.</p></div> </dt>
<dd>
<p>
- Specify how differences in submodules are shown. When <code>--submodule</code>
- or <code>--submodule=log</code> is given, the <em>log</em> format is used. This format lists
- the commits in the range like <a href="git-submodule.html">git-submodule(1)</a> <code>summary</code> does.
- Omitting the <code>--submodule</code> option or specifying <code>--submodule=short</code>,
+ Specify how differences in submodules are shown. When <tt>--submodule</tt>
+ or <tt>--submodule=log</tt> is given, the <em>log</em> format is used. This format lists
+ the commits in the range like <a href="git-submodule.html">git-submodule(1)</a> <tt>summary</tt> does.
+ Omitting the <tt>--submodule</tt> option or specifying <tt>--submodule=short</tt>,
uses the <em>short</em> format. This format just shows the names of the commits
at the beginning and end of the range. Can be tweaked via the
- <code>diff.submodule</code> configuration variable.
+ <tt>diff.submodule</tt> configuration variable.
</p>
</dd>
<dt class="hdlist1">
@@ -2951,8 +2955,8 @@ any of those replacements occurred.</p></div> <dd>
<p>
Show colored diff.
- <code>--color</code> (i.e. without <em>=<when></em>) is the same as <code>--color=always</code>.
- <em><when></em> can be one of <code>always</code>, <code>never</code>, or <code>auto</code>.
+ <tt>--color</tt> (i.e. without <em>=<when></em>) is the same as <tt>--color=always</tt>.
+ <em><when></em> can be one of <tt>always</tt>, <tt>never</tt>, or <tt>auto</tt>.
</p>
</dd>
<dt class="hdlist1">
@@ -2961,7 +2965,7 @@ any of those replacements occurred.</p></div> <dd>
<p>
Turn off colored diff.
- It is the same as <code>--color=never</code>.
+ It is the same as <tt>--color=never</tt>.
</p>
</dd>
<dt class="hdlist1">
@@ -2971,7 +2975,7 @@ any of those replacements occurred.</p></div> <p>
Show a word diff, using the <mode> to delimit changed words.
By default, words are delimited by whitespace; see
- <code>--word-diff-regex</code> below. The <mode> defaults to <em>plain</em>, and
+ <tt>--word-diff-regex</tt> below. The <mode> defaults to <em>plain</em>, and
must be one of:
</p>
<div class="openblock">
@@ -2982,7 +2986,7 @@ color </dt>
<dd>
<p>
- Highlight changed words using only colors. Implies <code>--color</code>.
+ Highlight changed words using only colors. Implies <tt>--color</tt>.
</p>
</dd>
<dt class="hdlist1">
@@ -2990,7 +2994,7 @@ plain </dt>
<dd>
<p>
- Show words as <code>[-removed-]</code> and <code>{+added+}</code>. Makes no
+ Show words as <tt>[-removed-]</tt> and <tt>{+added+}</tt>. Makes no
attempts to escape the delimiters if they appear in the input,
so the output may be ambiguous.
</p>
@@ -3002,10 +3006,10 @@ porcelain <p>
Use a special line-based format intended for script
consumption. Added/removed/unchanged runs are printed in the
- usual unified diff format, starting with a <code>+</code>/<code>-</code>/` `
+ usual unified diff format, starting with a <tt>+</tt>/<tt>-</tt>/` `
character at the beginning of the line and extending to the
end of the line. Newlines in the input are represented by a
- tilde <code>~</code> on a line of its own.
+ tilde <tt>~</tt> on a line of its own.
</p>
</dd>
<dt class="hdlist1">
@@ -3028,12 +3032,12 @@ highlight the changed parts in all modes if enabled.</p></div> <p>
Use <regex> to decide what a word is, instead of considering
runs of non-whitespace to be a word. Also implies
- <code>--word-diff</code> unless it was already enabled.
+ <tt>--word-diff</tt> unless it was already enabled.
</p>
<div class="paragraph"><p>Every non-overlapping match of the
<regex> is considered a word. Anything between these matches is
considered whitespace and ignored(!) for the purposes of finding
-differences. You may want to append <code>|[^[:space:]]</code> to your regular
+differences. You may want to append <tt>|[^[:space:]]</tt> to your regular
expression to make sure that it matches all non-whitespace characters.
A match that contains a newline is silently truncated(!) at the
newline.</p></div>
@@ -3047,8 +3051,8 @@ override configuration settings.</p></div> </dt>
<dd>
<p>
- Equivalent to <code>--word-diff=color</code> plus (if a regex was
- specified) <code>--word-diff-regex=<regex></code>.
+ Equivalent to <tt>--word-diff=color</tt> plus (if a regex was
+ specified) <tt>--word-diff-regex=<regex></tt>.
</p>
</dd>
<dt class="hdlist1">
@@ -3066,7 +3070,7 @@ override configuration settings.</p></div> <dd>
<p>
Warn if changes introduce whitespace errors. What are
- considered whitespace errors is controlled by <code>core.whitespace</code>
+ considered whitespace errors is controlled by <tt>core.whitespace</tt>
configuration. By default, trailing whitespaces (including
lines that solely consist of whitespaces) and a space character
that is immediately followed by a tab character inside the
@@ -3090,8 +3094,8 @@ override configuration settings.</p></div> </dt>
<dd>
<p>
- In addition to <code>--full-index</code>, output a binary diff that
- can be applied with <code>git-apply</code>.
+ In addition to <tt>--full-index</tt>, output a binary diff that
+ can be applied with <tt>git-apply</tt>.
</p>
</dd>
<dt class="hdlist1">
@@ -3102,9 +3106,9 @@ override configuration settings.</p></div> Instead of showing the full 40-byte hexadecimal object
name in diff-raw format output and diff-tree header
lines, show only a partial prefix. This is
- independent of the <code>--full-index</code> option above, which controls
+ independent of the <tt>--full-index</tt> option above, which controls
the diff-patch output format. Non default number of
- digits can be specified with <code>--abbrev=<n></code>.
+ digits can be specified with <tt>--abbrev=<n></tt>.
</p>
</dd>
<dt class="hdlist1">
@@ -3122,15 +3126,15 @@ override configuration settings.</p></div> not as a series of deletion and insertion mixed together with a very
few lines that happen to match textually as the context, but as a
single deletion of everything old followed by a single insertion of
-everything new, and the number <code>m</code> controls this aspect of the -B
-option (defaults to 60%). <code>-B/70%</code> specifies that less than 30% of the
+everything new, and the number <tt>m</tt> controls this aspect of the -B
+option (defaults to 60%). <tt>-B/70%</tt> specifies that less than 30% of the
original should remain in the result for Git to consider it a total
rewrite (i.e. otherwise the resulting patch will be a series of
deletion and insertion mixed together with context lines).</p></div>
<div class="paragraph"><p>When used with -M, a totally-rewritten file is also considered as the
source of a rename (usually -M only considers a file that disappeared
-as the source of a rename), and the number <code>n</code> controls this aspect of
-the -B option (defaults to 50%). <code>-B20%</code> specifies that a change with
+as the source of a rename), and the number <tt>n</tt> controls this aspect of
+the -B option (defaults to 50%). <tt>-B20%</tt> specifies that a change with
addition and deletion compared to 20% or more of the file’s size are
eligible for being picked up as a possible source of a rename to
another file.</p></div>
@@ -3145,16 +3149,16 @@ another file.</p></div> <p>
If generating diffs, detect and report renames for each commit.
For following files across renames while traversing history, see
- <code>--follow</code>.
- If <code>n</code> is specified, it is a threshold on the similarity
+ <tt>--follow</tt>.
+ If <tt>n</tt> is specified, it is a threshold on the similarity
index (i.e. amount of addition/deletions compared to the
- file’s size). For example, <code>-M90%</code> means Git should consider a
+ file’s size). For example, <tt>-M90%</tt> means Git should consider a
delete/add pair to be a rename if more than 90% of the file
- hasn’t changed. Without a <code>%</code> sign, the number is to be read as
- a fraction, with a decimal point before it. I.e., <code>-M5</code> becomes
- 0.5, and is thus the same as <code>-M50%</code>. Similarly, <code>-M05</code> is
- the same as <code>-M5%</code>. To limit detection to exact renames, use
- <code>-M100%</code>. The default similarity index is 50%.
+ hasn’t changed. Without a <tt>%</tt> sign, the number is to be read as
+ a fraction, with a decimal point before it. I.e., <tt>-M5</tt> becomes
+ 0.5, and is thus the same as <tt>-M50%</tt>. Similarly, <tt>-M05</tt> is
+ the same as <tt>-M5%</tt>. To limit detection to exact renames, use
+ <tt>-M100%</tt>. The default similarity index is 50%.
</p>
</dd>
<dt class="hdlist1">
@@ -3165,8 +3169,8 @@ another file.</p></div> </dt>
<dd>
<p>
- Detect copies as well as renames. See also <code>--find-copies-harder</code>.
- If <code>n</code> is specified, it has the same meaning as for <code>-M<n></code>.
+ Detect copies as well as renames. See also <tt>--find-copies-harder</tt>.
+ If <tt>n</tt> is specified, it has the same meaning as for <tt>-M<n></tt>.
</p>
</dd>
<dt class="hdlist1">
@@ -3174,13 +3178,13 @@ another file.</p></div> </dt>
<dd>
<p>
- For performance reasons, by default, <code>-C</code> option finds copies only
+ For performance reasons, by default, <tt>-C</tt> option finds copies only
if the original file of the copy was modified in the same
changeset. This flag makes the command
inspect unmodified files as candidates for the source of
copy. This is a very expensive operation for large
projects, so use it with caution. Giving more than one
- <code>-C</code> option has the same effect.
+ <tt>-C</tt> option has the same effect.
</p>
</dd>
<dt class="hdlist1">
@@ -3192,14 +3196,14 @@ another file.</p></div> <dd>
<p>
Omit the preimage for deletes, i.e. print only the header but not
- the diff between the preimage and <code>/dev/null</code>. The resulting patch
- is not meant to be applied with <code>patch</code> nor <code>git apply</code>; this is
+ the diff between the preimage and <tt>/dev/null</tt>. The resulting patch
+ is not meant to be applied with <tt>patch</tt> nor <tt>git apply</tt>; this is
solely for people who want to just concentrate on reviewing the
text after the change. In addition, the output obviously lack
enough information to apply such a patch in reverse, even manually,
hence the name of the option.
</p>
-<div class="paragraph"><p>When used together with <code>-B</code>, omit also the preimage in the deletion part
+<div class="paragraph"><p>When used together with <tt>-B</tt>, omit also the preimage in the deletion part
of a delete/create pair.</p></div>
</dd>
<dt class="hdlist1">
@@ -3207,7 +3211,7 @@ of a delete/create pair.</p></div> </dt>
<dd>
<p>
- The <code>-M</code> and <code>-C</code> options require O(n^2) processing time where n
+ The <tt>-M</tt> and <tt>-C</tt> options require O(n^2) processing time where n
is the number of potential rename/copy targets. This
option prevents rename/copy detection from running if
the number of rename/copy targets exceeds the specified
@@ -3219,13 +3223,13 @@ of a delete/create pair.</p></div> </dt>
<dd>
<p>
- Select only files that are Added (<code>A</code>), Copied (<code>C</code>),
- Deleted (<code>D</code>), Modified (<code>M</code>), Renamed (<code>R</code>), have their
- type (i.e. regular file, symlink, submodule, …) changed (<code>T</code>),
- are Unmerged (<code>U</code>), are
- Unknown (<code>X</code>), or have had their pairing Broken (<code>B</code>).
+ Select only files that are Added (<tt>A</tt>), Copied (<tt>C</tt>),
+ Deleted (<tt>D</tt>), Modified (<tt>M</tt>), Renamed (<tt>R</tt>), have their
+ type (i.e. regular file, symlink, submodule, …) changed (<tt>T</tt>),
+ are Unmerged (<tt>U</tt>), are
+ Unknown (<tt>X</tt>), or have had their pairing Broken (<tt>B</tt>).
Any combination of the filter characters (including none) can be used.
- When <code>*</code> (All-or-none) is added to the combination, all
+ When <tt>*</tt> (All-or-none) is added to the combination, all
paths are selected if there is any file that matches
other criteria in the comparison; if there is no file
that matches other criteria, nothing is selected.
@@ -3243,7 +3247,7 @@ of a delete/create pair.</p></div> <div class="paragraph"><p>It is useful when you’re looking for an exact block of code (like a
struct), and want to know the history of that block since it first
came into being: use the feature iteratively to feed the interesting
-block in the preimage back into <code>-S</code>, and keep going until you get the
+block in the preimage back into <tt>-S</tt>, and keep going until you get the
very first version of the block.</p></div>
</dd>
<dt class="hdlist1">
@@ -3254,17 +3258,17 @@ very first version of the block.</p></div> Look for differences whose patch text contains added/removed
lines that match <regex>.
</p>
-<div class="paragraph"><p>To illustrate the difference between <code>-S<regex> --pickaxe-regex</code> and
-<code>-G<regex></code>, consider a commit with the following diff in the same
+<div class="paragraph"><p>To illustrate the difference between <tt>-S<regex> --pickaxe-regex</tt> and
+<tt>-G<regex></tt>, consider a commit with the following diff in the same
file:</p></div>
<div class="listingblock">
<div class="content">
-<pre><code>+ return !regexec(regexp, two->ptr, 1, &regmatch, 0);
+<pre><tt>+ return !regexec(regexp, two->ptr, 1, &regmatch, 0);
...
-- hit = !regexec(regexp, mf2.ptr, 1, &regmatch, 0);</code></pre>
+- hit = !regexec(regexp, mf2.ptr, 1, &regmatch, 0);</tt></pre>
</div></div>
-<div class="paragraph"><p>While <code>git log -G"regexec\(regexp"</code> will show this commit, <code>git log
--S"regexec\(regexp" --pickaxe-regex</code> will not (because the number of
+<div class="paragraph"><p>While <tt>git log -G"regexec\(regexp"</tt> will show this commit, <tt>git log
+-S"regexec\(regexp" --pickaxe-regex</tt> will not (because the number of
occurrences of that string did not change).</p></div>
<div class="paragraph"><p>See the <em>pickaxe</em> entry in <a href="gitdiffcore.html">gitdiffcore(7)</a> for more
information.</p></div>
@@ -3274,7 +3278,7 @@ information.</p></div> </dt>
<dd>
<p>
- When <code>-S</code> or <code>-G</code> finds a change, show all the changes in that
+ When <tt>-S</tt> or <tt>-G</tt> finds a change, show all the changes in that
changeset, not just the files that contain the change
in <string>.
</p>
@@ -3284,7 +3288,7 @@ information.</p></div> </dt>
<dd>
<p>
- Treat the <string> given to <code>-S</code> as an extended POSIX regular
+ Treat the <string> given to <tt>-S</tt> as an extended POSIX regular
expression to match.
</p>
</dd>
@@ -3295,9 +3299,9 @@ information.</p></div> <p>
Output the patch in the order specified in the
<orderfile>, which has one shell glob pattern per line.
- This overrides the <code>diff.orderfile</code> configuration variable
- (see <a href="git-config.html">git-config(1)</a>). To cancel <code>diff.orderfile</code>,
- use <code>-O/dev/null</code>.
+ This overrides the <tt>diff.orderfile</tt> configuration variable
+ (see <a href="git-config.html">git-config(1)</a>). To cancel <tt>diff.orderfile</tt>,
+ use <tt>-O/dev/null</tt>.
</p>
</dd>
<dt class="hdlist1">
@@ -3496,12 +3500,12 @@ It is preceded with a "git diff" header that looks like this: </p>
<div class="literalblock">
<div class="content">
-<pre><code>diff --git a/file1 b/file2</code></pre>
+<pre><tt>diff --git a/file1 b/file2</tt></pre>
</div></div>
-<div class="paragraph"><p>The <code>a/</code> and <code>b/</code> filenames are the same unless rename/copy is
+<div class="paragraph"><p>The <tt>a/</tt> and <tt>b/</tt> filenames are the same unless rename/copy is
involved. Especially, even for a creation or a deletion,
-<code>/dev/null</code> is <em>not</em> used in place of the <code>a/</code> or <code>b/</code> filenames.</p></div>
-<div class="paragraph"><p>When rename/copy is involved, <code>file1</code> and <code>file2</code> show the
+<tt>/dev/null</tt> is <em>not</em> used in place of the <tt>a/</tt> or <tt>b/</tt> filenames.</p></div>
+<div class="paragraph"><p>When rename/copy is involved, <tt>file1</tt> and <tt>file2</tt> show the
name of the source file of the rename/copy and the name of
the file that rename/copy produces, respectively.</p></div>
</li>
@@ -3511,7 +3515,7 @@ It is followed by one or more extended header lines: </p>
<div class="literalblock">
<div class="content">
-<pre><code>old mode <mode>
+<pre><tt>old mode <mode>
new mode <mode>
deleted file mode <mode>
new file mode <mode>
@@ -3521,11 +3525,11 @@ rename from <path> rename to <path>
similarity index <number>
dissimilarity index <number>
-index <hash>..<hash> <mode></code></pre>
+index <hash>..<hash> <mode></tt></pre>
</div></div>
<div class="paragraph"><p>File modes are printed as 6-digit octal numbers including the file type
and file permission bits.</p></div>
-<div class="paragraph"><p>Path names in extended headers do not include the <code>a/</code> and <code>b/</code> prefixes.</p></div>
+<div class="paragraph"><p>Path names in extended headers do not include the <tt>a/</tt> and <tt>b/</tt> prefixes.</p></div>
<div class="paragraph"><p>The similarity index is the percentage of unchanged lines, and
the dissimilarity index is the percentage of changed lines. It
is a rounded down integer, followed by a percent sign. The
@@ -3539,26 +3543,26 @@ separate lines indicate the old and the new mode.</p></div> <li>
<p>
TAB, LF, double quote and backslash characters in pathnames
- are represented as <code>\t</code>, <code>\n</code>, <code>\"</code> and <code>\\</code>, respectively.
+ are represented as <tt>\t</tt>, <tt>\n</tt>, <tt>\"</tt> and <tt>\\</tt>, respectively.
If there is need for such substitution then the whole
pathname is put in double quotes.
</p>
</li>
<li>
<p>
-All the <code>file1</code> files in the output refer to files before the
- commit, and all the <code>file2</code> files refer to files after the commit.
+All the <tt>file1</tt> files in the output refer to files before the
+ commit, and all the <tt>file2</tt> files refer to files after the commit.
It is incorrect to apply each change to each file sequentially. For
example, this patch will swap a and b:
</p>
<div class="literalblock">
<div class="content">
-<pre><code>diff --git a/a b/b
+<pre><tt>diff --git a/a b/b
rename from a
rename to b
diff --git a/b b/a
rename from b
-rename to a</code></pre>
+rename to a</tt></pre>
</div></div>
</li>
</ol></div>
@@ -3567,7 +3571,7 @@ rename to a</code></pre> <div class="sect1">
<h2 id="_combined_diff_format">combined diff format</h2>
<div class="sectionbody">
-<div class="paragraph"><p>Any diff-generating command can take the ‘-c` or <code>--cc</code> option to
+<div class="paragraph"><p>Any diff-generating command can take the ‘-c` or <tt>--cc</tt> option to
produce a <em>combined diff</em> when showing a merge. This is the default
format when showing merges with <a href="git-diff.html">git-diff(1)</a> or
<a href="git-show.html">git-show(1)</a>. Note also that you can give the `-m’ option to any
@@ -3576,7 +3580,7 @@ of a merge.</p></div> <div class="paragraph"><p>A <em>combined diff</em> format looks like this:</p></div>
<div class="listingblock">
<div class="content">
-<pre><code>diff --combined describe.c
+<pre><tt>diff --combined describe.c
index fabadb8,cc95eb0..4866510
--- a/describe.c
+++ b/describe.c
@@ -3602,7 +3606,7 @@ index fabadb8,cc95eb0..4866510 +
if (!initialized) {
initialized = 1;
- for_each_ref(get_name);</code></pre>
+ for_each_ref(get_name);</tt></pre>
</div></div>
<div class="olist arabic"><ol class="arabic">
<li>
@@ -3612,12 +3616,12 @@ It is preceded with a "git diff" header, that looks like </p>
<div class="literalblock">
<div class="content">
-<pre><code>diff --combined file</code></pre>
+<pre><tt>diff --combined file</tt></pre>
</div></div>
<div class="paragraph"><p>or like this (when <em>--cc</em> option is used):</p></div>
<div class="literalblock">
<div class="content">
-<pre><code>diff --cc file</code></pre>
+<pre><tt>diff --cc file</tt></pre>
</div></div>
</li>
<li>
@@ -3627,12 +3631,12 @@ It is followed by one or more extended header lines </p>
<div class="literalblock">
<div class="content">
-<pre><code>index <hash>,<hash>..<hash>
+<pre><tt>index <hash>,<hash>..<hash>
mode <mode>,<mode>..<mode>
new file mode <mode>
-deleted file mode <mode>,<mode></code></pre>
+deleted file mode <mode>,<mode></tt></pre>
</div></div>
-<div class="paragraph"><p>The <code>mode <mode>,<mode>..<mode></code> line appears only if at least one of
+<div class="paragraph"><p>The <tt>mode <mode>,<mode>..<mode></tt> line appears only if at least one of
the <mode> is different from the rest. Extended headers with
information about detected contents movement (renames and
copying detection) are designed to work with diff of two
@@ -3644,49 +3648,49 @@ It is followed by two-line from-file/to-file header </p>
<div class="literalblock">
<div class="content">
-<pre><code>--- a/file
-+++ b/file</code></pre>
+<pre><tt>--- a/file
++++ b/file</tt></pre>
</div></div>
<div class="paragraph"><p>Similar to two-line header for traditional <em>unified</em> diff
-format, <code>/dev/null</code> is used to signal created or deleted
+format, <tt>/dev/null</tt> is used to signal created or deleted
files.</p></div>
</li>
<li>
<p>
Chunk header format is modified to prevent people from
- accidentally feeding it to <code>patch -p1</code>. Combined diff format
+ accidentally feeding it to <tt>patch -p1</tt>. Combined diff format
was created for review of merge commit changes, and was not
meant for apply. The change is similar to the change in the
extended <em>index</em> header:
</p>
<div class="literalblock">
<div class="content">
-<pre><code>@@@ <from-file-range> <from-file-range> <to-file-range> @@@</code></pre>
+<pre><tt>@@@ <from-file-range> <from-file-range> <to-file-range> @@@</tt></pre>
</div></div>
-<div class="paragraph"><p>There are (number of parents + 1) <code>@</code> characters in the chunk
+<div class="paragraph"><p>There are (number of parents + 1) <tt>@</tt> characters in the chunk
header for combined diff format.</p></div>
</li>
</ol></div>
<div class="paragraph"><p>Unlike the traditional <em>unified</em> diff format, which shows two
-files A and B with a single column that has <code>-</code> (minus — appears in A but removed in B), <code>+</code> (plus — missing in A but
-added to B), or <code>" "</code> (space — unchanged) prefix, this format
+files A and B with a single column that has <tt>-</tt> (minus — appears in A but removed in B), <tt>+</tt> (plus — missing in A but
+added to B), or <tt>" "</tt> (space — unchanged) prefix, this format
compares two or more files file1, file2,… with one file X, and
shows how X differs from each of fileN. One column for each of
fileN is prepended to the output line to note how X’s line is
different from it.</p></div>
-<div class="paragraph"><p>A <code>-</code> character in the column N means that the line appears in
-fileN but it does not appear in the result. A <code>+</code> character
+<div class="paragraph"><p>A <tt>-</tt> character in the column N means that the line appears in
+fileN but it does not appear in the result. A <tt>+</tt> character
in the column N means that the line appears in the result,
and fileN does not have that line (in other words, the line was
added, from the point of view of that parent).</p></div>
<div class="paragraph"><p>In the above example output, the function signature was changed
-from both files (hence two <code>-</code> removals from both file1 and
-file2, plus <code>++</code> to mean one line that was added does not appear
+from both files (hence two <tt>-</tt> removals from both file1 and
+file2, plus <tt>++</tt> to mean one line that was added does not appear
in either file1 nor file2). Also eight other lines are the same
-from file1 but do not appear in file2 (hence prefixed with <code>+</code>).</p></div>
-<div class="paragraph"><p>When shown by <code>git diff-tree -c</code>, it compares the parents of a
+from file1 but do not appear in file2 (hence prefixed with <tt>+</tt>).</p></div>
+<div class="paragraph"><p>When shown by <tt>git diff-tree -c</tt>, it compares the parents of a
merge commit with the merge result (i.e. file1..fileN are the
-parents). When shown by <code>git diff-files -c</code>, it compares the
+parents). When shown by <tt>git diff-files -c</tt>, it compares the
two unresolved merge parents with the working tree file
(i.e. file1 is stage 2 aka "our version", file2 is stage 3 aka
"their version").</p></div>
@@ -3697,7 +3701,7 @@ two unresolved merge parents with the working tree file <div class="sectionbody">
<div class="dlist"><dl>
<dt class="hdlist1">
-<code>git log --no-merges</code>
+<tt>git log --no-merges</tt>
</dt>
<dd>
<p>
@@ -3705,16 +3709,16 @@ two unresolved merge parents with the working tree file </p>
</dd>
<dt class="hdlist1">
-<code>git log v2.6.12.. include/scsi drivers/scsi</code>
+<tt>git log v2.6.12.. include/scsi drivers/scsi</tt>
</dt>
<dd>
<p>
Show all commits since version <em>v2.6.12</em> that changed any file
- in the <code>include/scsi</code> or <code>drivers/scsi</code> subdirectories
+ in the <tt>include/scsi</tt> or <tt>drivers/scsi</tt> subdirectories
</p>
</dd>
<dt class="hdlist1">
-<code>git log --since="2 weeks ago" -- gitk</code>
+<tt>git log --since="2 weeks ago" -- gitk</tt>
</dt>
<dd>
<p>
@@ -3724,7 +3728,7 @@ two unresolved merge parents with the working tree file </p>
</dd>
<dt class="hdlist1">
-<code>git log --name-status release..test</code>
+<tt>git log --name-status release..test</tt>
</dt>
<dd>
<p>
@@ -3734,17 +3738,17 @@ two unresolved merge parents with the working tree file </p>
</dd>
<dt class="hdlist1">
-<code>git log --follow builtin/rev-list.c</code>
+<tt>git log --follow builtin/rev-list.c</tt>
</dt>
<dd>
<p>
- Shows the commits that changed <code>builtin/rev-list.c</code>, including
+ Shows the commits that changed <tt>builtin/rev-list.c</tt>, including
those commits that occurred before the file was given its
present name.
</p>
</dd>
<dt class="hdlist1">
-<code>git log --branches --not --remotes=origin</code>
+<tt>git log --branches --not --remotes=origin</tt>
</dt>
<dd>
<p>
@@ -3754,7 +3758,7 @@ two unresolved merge parents with the working tree file </p>
</dd>
<dt class="hdlist1">
-<code>git log master --not --remotes=*/master</code>
+<tt>git log master --not --remotes=*/master</tt>
</dt>
<dd>
<p>
@@ -3763,7 +3767,7 @@ two unresolved merge parents with the working tree file </p>
</dd>
<dt class="hdlist1">
-<code>git log -p -m --first-parent</code>
+<tt>git log -p -m --first-parent</tt>
</dt>
<dd>
<p>
@@ -3775,16 +3779,16 @@ two unresolved merge parents with the working tree file </p>
</dd>
<dt class="hdlist1">
-<code>git log -L '/int main/',/^}/:main.c</code>
+<tt>git log -L '/int main/',/^}/:main.c</tt>
</dt>
<dd>
<p>
- Shows how the function <code>main()</code> in the file <code>main.c</code> evolved
+ Shows how the function <tt>main()</tt> in the file <tt>main.c</tt> evolved
over time.
</p>
</dd>
<dt class="hdlist1">
-<code>git log -3</code>
+<tt>git log -3</tt>
</dt>
<dd>
<p>
@@ -3836,33 +3840,33 @@ mind.</p></div> a warning if the commit log message given to it does not look
like a valid UTF-8 string, unless you explicitly say your
project uses a legacy encoding. The way to say this is to
- have i18n.commitencoding in <code>.git/config</code> file, like this:
+ have i18n.commitencoding in <tt>.git/config</tt> file, like this:
</p>
<div class="listingblock">
<div class="content">
-<pre><code>[i18n]
- commitencoding = ISO-8859-1</code></pre>
+<pre><tt>[i18n]
+ commitencoding = ISO-8859-1</tt></pre>
</div></div>
<div class="paragraph"><p>Commit objects created with the above setting record the value
-of <code>i18n.commitencoding</code> in its <code>encoding</code> header. This is to
+of <tt>i18n.commitencoding</tt> in its <tt>encoding</tt> header. This is to
help other people who look at them later. Lack of this header
implies that the commit log message is encoded in UTF-8.</p></div>
</li>
<li>
<p>
<em>git log</em>, <em>git show</em>, <em>git blame</em> and friends look at the
- <code>encoding</code> header of a commit object, and try to re-code the
+ <tt>encoding</tt> header of a commit object, and try to re-code the
log message into UTF-8 unless otherwise specified. You can
specify the desired output encoding with
- <code>i18n.logoutputencoding</code> in <code>.git/config</code> file, like this:
+ <tt>i18n.logoutputencoding</tt> in <tt>.git/config</tt> file, like this:
</p>
<div class="listingblock">
<div class="content">
-<pre><code>[i18n]
- logoutputencoding = ISO-8859-1</code></pre>
+<pre><tt>[i18n]
+ logoutputencoding = ISO-8859-1</tt></pre>
</div></div>
<div class="paragraph"><p>If you do not have this configuration variable, the value of
-<code>i18n.commitencoding</code> is used instead.</p></div>
+<tt>i18n.commitencoding</tt> is used instead.</p></div>
</li>
</ol></div>
<div class="paragraph"><p>Note that we deliberately chose not to re-code the commit log
@@ -3882,8 +3886,8 @@ format.pretty </dt>
<dd>
<p>
- Default for the <code>--format</code> option. (See <em>Pretty Formats</em> above.)
- Defaults to <code>medium</code>.
+ Default for the <tt>--format</tt> option. (See <em>Pretty Formats</em> above.)
+ Defaults to <tt>medium</tt>.
</p>
</dd>
<dt class="hdlist1">
@@ -3892,7 +3896,7 @@ i18n.logOutputEncoding <dd>
<p>
Encoding to use when displaying logs. (See <em>Discussion</em> above.)
- Defaults to the value of <code>i18n.commitEncoding</code> if set, and UTF-8
+ Defaults to the value of <tt>i18n.commitEncoding</tt> if set, and UTF-8
otherwise.
</p>
</dd>
@@ -3902,8 +3906,8 @@ log.date <dd>
<p>
Default format for human-readable dates. (Compare the
- <code>--date</code> option.) Defaults to "default", which means to write
- dates like <code>Sat May 8 19:35:34 2010 -0500</code>.
+ <tt>--date</tt> option.) Defaults to "default", which means to write
+ dates like <tt>Sat May 8 19:35:34 2010 -0500</tt>.
</p>
</dd>
<dt class="hdlist1">
@@ -3911,10 +3915,10 @@ log.showroot </dt>
<dd>
<p>
- If <code>false</code>, <code>git log</code> and related commands will not treat the
+ If <tt>false</tt>, <tt>git log</tt> and related commands will not treat the
initial commit as a big creation event. Any root commits in
- <code>git log -p</code> output would be shown without a diff attached.
- The default is <code>true</code>.
+ <tt>git log -p</tt> output would be shown without a diff attached.
+ The default is <tt>true</tt>.
</p>
</dd>
<dt class="hdlist1">
@@ -3930,17 +3934,17 @@ notes.displayRef </dt>
<dd>
<p>
- Which refs, in addition to the default set by <code>core.notesRef</code>
+ Which refs, in addition to the default set by <tt>core.notesRef</tt>
or <em>GIT_NOTES_REF</em>, to read notes from when showing commit
- messages with the <code>log</code> family of commands. See
+ messages with the <tt>log</tt> family of commands. See
<a href="git-notes.html">git-notes(1)</a>.
</p>
<div class="paragraph"><p>May be an unabbreviated ref name or a glob and may be specified
multiple times. A warning will be issued for refs that do not exist,
but a glob that does not match any refs is silently ignored.</p></div>
-<div class="paragraph"><p>This setting can be disabled by the <code>--no-notes</code> option,
+<div class="paragraph"><p>This setting can be disabled by the <tt>--no-notes</tt> option,
overridden by the <em>GIT_NOTES_DISPLAY_REF</em> environment variable,
-and overridden by the <code>--notes=<ref></code> option.</p></div>
+and overridden by the <tt>--notes=<ref></tt> option.</p></div>
</dd>
</dl></div>
</div>
|