Autogenerated HTML docs for v1.8.5.1-19-gdaad3

1 files changed, 80 insertions, 81 deletions

diff --git a/git-rev-list.html b/git-rev-list.html
index 516f47b1f..1dd6fb95d 100644
--- a/git-rev-list.html
+++ b/git-rev-list.html
@@ -958,7 +958,7 @@ if it is part of the log message.</p></div>
 </dt>

 <dd>

 <p>

-        Limit the commits output to ones that match all given --grep,

+        Limit the commits output to ones that match all given <code>--grep</code>,

         instead of ones that match at least one.

 </p>

 </dd>

@@ -970,7 +970,8 @@ if it is part of the log message.</p></div>
 </dt>

 <dd>

 <p>

-        Match the regexp limiting patterns without regard to letters case.

+        Match the regular expression limiting patterns without regard to letter

+        case.

 </p>

 </dd>

 <dt class="hdlist1">

@@ -1011,7 +1012,7 @@ if it is part of the log message.</p></div>
 </dt>

 <dd>

 <p>

-        Consider the limiting patterns to be Perl-compatible regexp.

+        Consider the limiting patterns to be Perl-compatible regular expressions.

         Requires libpcre to be compiled in.

 </p>

 </dd>

@@ -1083,7 +1084,7 @@ parents) and <code>--max-parents=-1</code> (negative numbers denote no upper lim
 <dd>

 <p>

         Reverses the meaning of the <em>&#94;</em> prefix (or lack thereof)

-        for all following revision specifiers, up to the next <em>--not</em>.

+        for all following revision specifiers, up to the next <code>--not</code>.

 </p>

 </dd>

 <dt class="hdlist1">

@@ -1168,7 +1169,7 @@ parents) and <code>--max-parents=-1</code> (negative numbers denote no upper lim
         is primarily meant to allow the caller to

         test the exit status to see if a range of objects is fully

         connected (or not).  It is faster than redirecting stdout

-        to /dev/null as the output does not have to be formatted.

+        to <code>/dev/null</code> as the output does not have to be formatted.

 </p>

 </dd>

 <dt class="hdlist1">

@@ -1186,15 +1187,15 @@ parents) and <code>--max-parents=-1</code> (negative numbers denote no upper lim
 <dd>

 <p>

         Omit any commit that introduces the same change as

-        another commit on the "other side" when the set of

+        another commit on the &#8220;other side&#8221; 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

 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).  It however shows the commits that were cherry-picked

-from the other branch (for example, "3rd on b" may be cherry-picked

-from branch A).  With this option, such pairs of commits are

+the <code>--left-right</code> option). However, it shows the commits that were

+cherry-picked from the other branch (for example, &#8220;3rd on b&#8221; may be

+cherry-picked from branch A). With this option, such pairs of commits are

 excluded from the output.</p></div>

 </dd>

 <dt class="hdlist1">

@@ -1241,14 +1242,14 @@ list.</p></div>
         exclude (that is, <em>&#94;commit</em>, <em>commit1..commit2</em>,

         nor <em>commit1...commit2</em> notations cannot be used).

 </p>

-<div class="paragraph"><p>With <em>--pretty</em> format other than oneline (for obvious reasons),

+<div class="paragraph"><p>With <code>--pretty</code> format other than <code>oneline</code> (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 <em>--pretty=oneline</em>, the commit message is

+instead.  Under <code>--pretty=oneline</code>, the commit message is

 prefixed with this information on the same line.

-This option cannot be combined with <em>--reverse</em>.

+This option cannot be combined with <code>--reverse</code>.

 See also <a href="git-reflog.html">git-reflog(1)</a>.</p></div>

 </dd>

 <dt class="hdlist1">

@@ -1341,7 +1342,7 @@ Default mode
 </dt>

 <dd>

 <p>

-        Additional option to <em>--full-history</em> to remove some needless

+        Additional option to <code>--full-history</code> to remove some needless

         merges from the resulting history, as there are no selected

         commits contributing to this merge.

 </p>

@@ -1380,13 +1381,13 @@ each merge.  The commits are:</p></div>
 <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

+  &#8220;asdf&#8221;, and a file <code>quux</code> exists with contents &#8220;quux&#8221;. Initial

   commits are compared to an empty tree, so <code>I</code> is !TREESAME.

 </p>

 </li>

 <li>

 <p>

-In <code>A</code>, <code>foo</code> contains just "foo".

+In <code>A</code>, <code>foo</code> contains just &#8220;foo&#8221;.

 </p>

 </li>

 <li>

@@ -1397,20 +1398,20 @@ In <code>A</code>, <code>foo</code> contains just "foo".
 </li>

 <li>

 <p>

-<code>C</code> does not change <code>foo</code>, but its merge <code>N</code> changes it to "foobar",

+<code>C</code> does not change <code>foo</code>, but its merge <code>N</code> changes it to &#8220;foobar&#8221;,

   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.

+<code>D</code> sets <code>foo</code> to &#8220;baz&#8221;. Its merge <code>O</code> combines the strings from

+  <code>N</code> and <code>D</code> to &#8220;foobarbaz&#8221;; 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>.

+<code>E</code> changes <code>quux</code> to &#8220;xyzzy&#8221;, and its merge <code>P</code> combines the

+  strings to &#8220;quux xyzzy&#8221;. <code>P</code> is TREESAME to <code>O</code>, but not to <code>E</code>.

 </p>

 </li>

 <li>

@@ -1421,9 +1422,9 @@ In <code>A</code>, <code>foo</code> contains just "foo".
 </p>

 </li>

 </ul></div>

-<div class="paragraph"><p><em>rev-list</em> walks backwards through history, including or excluding

-commits based on whether <em>--full-history</em> and/or parent rewriting

-(via <em>--parents</em> or <em>--children</em>) are used.  The following settings

+<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

 are available.</p></div>

 <div class="dlist"><dl>

 <dt class="hdlist1">

@@ -1432,7 +1433,7 @@ Default mode
 <dd>

 <p>

         Commits are included if they are not TREESAME to any parent

-        (though this can be changed, see <em>--sparse</em> below).  If the

+        (though this can be changed, see <code>--sparse</code> 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

@@ -1449,7 +1450,7 @@ Default mode
 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 --parents, but that does

+<div class="paragraph"><p>Parent/child relations are only visible with <code>--parents</code>, but that does

 not affect the commits selected in default mode, so we have shown the

 parent lines.</p></div>

 </dd>

@@ -1481,7 +1482,7 @@ them disconnected.</p></div>
 <dd>

 <p>

         Ordinary commits are only included if they are !TREESAME

-        (though this can be changed, see <em>--sparse</em> below).

+        (though this can be changed, see <code>--sparse</code> 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

@@ -1494,7 +1495,7 @@ themselves.  This results in</p></div>
          \   /   /   /   /

           `-------------'</code></pre>

 </div></div>

-<div class="paragraph"><p>Compare to <em>--full-history</em> without rewriting above.  Note that <code>E</code>

+<div class="paragraph"><p>Compare to <code>--full-history</code> without rewriting above.  Note that <code>E</code>

 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>

@@ -1519,7 +1520,7 @@ affects inclusion:</p></div>
 <p>

         All commits that are walked are included.

 </p>

-<div class="paragraph"><p>Note that without <em>--full-history</em>, this still simplifies merges: if

+<div class="paragraph"><p>Note that without <code>--full-history</code>, 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>

@@ -1529,7 +1530,7 @@ sides of the merge are never walked.</p></div>
 <dd>

 <p>

         First, build a history graph in the same way that

-        <em>--full-history</em> with parent rewriting does (see above).

+        <code>--full-history</code> 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

 history according to the following rules:</p></div>

@@ -1559,7 +1560,7 @@ 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

-<em>--full-history</em> with parent rewriting.  The example turns into:</p></div>

+<code>--full-history</code> with parent rewriting.  The example turns into:</p></div>

 <div class="listingblock">

 <div class="content">

 <pre><code>          .-A---M---N---O

@@ -1568,7 +1569,7 @@ If after this parent rewriting, <code>C'</code> is a root or merge commit (has
          \   /       /

           `---------'</code></pre>

 </div></div>

-<div class="paragraph"><p>Note the major differences in <code>N</code>, <code>P</code> and <code>Q</code> over <em>--full-history</em>:</p></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="openblock">

 <div class="content">

 <div class="ulist"><ul>

@@ -1603,9 +1604,9 @@ If after this parent rewriting, <code>C'</code> is a root or merge commit (has
 <dd>

 <p>

         Limit the displayed commits to those directly on the ancestry

-        chain between the "from" and "to" commits in the given commit

-        range. I.e. only display commits that are ancestor of the "to"

-        commit, and descendants of the "from" commit.

+        chain between the &#8220;from&#8221; and &#8220;to&#8221; commits in the given commit

+        range. I.e. only display commits that are ancestor of the &#8220;to&#8221;

+        commit and descendants of the &#8220;from&#8221; commit.

 </p>

 <div class="paragraph"><p>As an example use case, consider the following commit history:</p></div>

 <div class="listingblock">

@@ -1619,13 +1620,13 @@ If after this parent rewriting, <code>C'</code> is a root or merge commit (has
 <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

+that &#8220;what does <code>M</code> have that did not exist in <code>D</code>&#8221;. The result in this

 example would be all the commits, except <code>A</code> and <code>B</code> (and <code>D</code> 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 <em>--ancestry-path</em>

+excluding <code>C</code> and <code>K</code>. This is exactly what the <code>--ancestry-path</code>

 option does. Applied to the <em>D..M</em> range, it results in:</p></div>

 <div class="listingblock">

 <div class="content">

@@ -1637,7 +1638,7 @@ option does. Applied to the <em>D..M</em> range, it results in:</p></div>
 </div></div>

 </dd>

 </dl></div>

-<div class="paragraph"><p>The <em>--simplify-by-decoration</em> option allows you to view only the

+<div class="paragraph"><p>The <code>--simplify-by-decoration</code> 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

@@ -1653,15 +1654,13 @@ commits are marked as TREESAME (subject to be simplified away).</p></div>
 </dt>

 <dd>

 <p>

-Limit output to the one commit object which is roughly halfway between

-included and excluded commits. Note that the bad bisection ref

-<code>refs/bisect/bad</code> is added to the included commits (if it

-exists) and the good bisection refs <code>refs/bisect/good-*</code> are

-added to the excluded commits (if they exist). Thus, supposing there

-are no refs in <code>refs/bisect/</code>, if

+        Limit output to the one commit object which is roughly halfway between

+        included and excluded commits. Note that the bad bisection ref

+        <code>refs/bisect/bad</code> is added to the included commits (if it

+        exists) and the good bisection refs <code>refs/bisect/good-*</code> are

+        added to the excluded commits (if they exist). Thus, supposing there

+        are no refs in <code>refs/bisect/</code>, if

 </p>

-</dd>

-</dl></div>

 <div class="listingblock">

 <div class="content">

 <pre><code>        $ git rev-list --bisect foo ^bar ^baz</code></pre>

@@ -1676,22 +1675,22 @@ are no refs in <code>refs/bisect/</code>, if
 introduces a regression is thus reduced to a binary search: repeatedly

 generate and test new 'midpoint&#8217;s until the commit chain is of length

 one.</p></div>

-<div class="dlist"><dl>

+</dd>

 <dt class="hdlist1">

 --bisect-vars

 </dt>

 <dd>

 <p>

-This calculates the same as <code>--bisect</code>, except that refs in

-<code>refs/bisect/</code> are not used, and except that this outputs

-text ready to be eval&#8217;ed by the shell. These lines will assign the

-name of the midpoint revision to the variable <code>bisect_rev</code>, and the

-expected number of commits to be tested after <code>bisect_rev</code> is tested

-to <code>bisect_nr</code>, the expected number of commits to be tested if

-<code>bisect_rev</code> turns out to be good to <code>bisect_good</code>, the expected

-number of commits to be tested if <code>bisect_rev</code> turns out to be bad to

-<code>bisect_bad</code>, and the number of commits we are bisecting right now to

-<code>bisect_all</code>.

+        This calculates the same as <code>--bisect</code>, except that refs in

+        <code>refs/bisect/</code> are not used, and except that this outputs

+        text ready to be eval&#8217;ed by the shell. These lines will assign the

+        name of the midpoint revision to the variable <code>bisect_rev</code>, and the

+        expected number of commits to be tested after <code>bisect_rev</code> is tested

+        to <code>bisect_nr</code>, the expected number of commits to be tested if

+        <code>bisect_rev</code> turns out to be good to <code>bisect_good</code>, the expected

+        number of commits to be tested if <code>bisect_rev</code> turns out to be bad to

+        <code>bisect_bad</code>, and the number of commits we are bisecting right now to

+        <code>bisect_all</code>.

 </p>

 </dd>

 <dt class="hdlist1">

@@ -1699,11 +1698,11 @@ number of commits to be tested if <code>bisect_rev</code> turns out to be bad to
 </dt>

 <dd>

 <p>

-This outputs all the commit objects between the included and excluded

-commits, ordered by their distance to the included and excluded

-commits. Refs in <code>refs/bisect/</code> are not used. The farthest

-from them is displayed first. (This is the only one displayed by

-<code>--bisect</code>.)

+        This outputs all the commit objects between the included and excluded

+        commits, ordered by their distance to the included and excluded

+        commits. Refs in <code>refs/bisect/</code> are not used. The farthest

+        from them is displayed first. (This is the only one displayed by

+        <code>--bisect</code>.)

 </p>

 <div class="paragraph"><p>This is useful because it makes it easy to choose a good commit to

 test when you want to avoid to test some of them for some reason (they

@@ -1766,7 +1765,7 @@ together.</p></div>
 <dd>

 <p>

         Output the commits in reverse order.

-        Cannot be combined with <em>--walk-reflogs</em>.

+        Cannot be combined with <code>--walk-reflogs</code>.

 </p>

 </dd>

 </dl></div>

@@ -1781,9 +1780,9 @@ together.</p></div>
 <dd>

 <p>

         Print the object IDs of any object referenced by the listed

-        commits.  <em>--objects foo ^bar</em> thus means "send me

+        commits.  <code>--objects foo ^bar</code> thus means &#8220;send me

         all object IDs which I need to download if I have the commit

-        object <em>bar</em>, but not <em>foo</em>".

+        object <em>bar</em> but not <em>foo</em>&#8221;.

 </p>

 </dd>

 <dt class="hdlist1">

@@ -1791,9 +1790,9 @@ together.</p></div>
 </dt>

 <dd>

 <p>

-        Similar to <em>--objects</em>, 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

+        Similar to <code>--objects</code>, but also print the IDs of excluded

+        commits prefixed with a &#8220;-&#8221; character.  This is used by

+        <a href="git-pack-objects.html">git-pack-objects(1)</a> to build &#8220;thin&#8221; pack, which records

         objects in deltified form based on objects contained in these

         excluded commits to reduce network traffic.

 </p>

@@ -1803,7 +1802,7 @@ together.</p></div>
 </dt>

 <dd>

 <p>

-        Only useful with <em>--objects</em>; print the object IDs that are not

+        Only useful with <code>--objects</code>; print the object IDs that are not

         in packs.

 </p>

 </dd>

@@ -1814,9 +1813,9 @@ 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

-        "unsorted" is given, the commits are show in the order they were

-        given on the command line. Otherwise (if "sorted" or no argument

-        was given), the commits are show in reverse chronological order

+        <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

+        was given), the commits are shown in reverse chronological order

         by commit time.

 </p>

 </dd>

@@ -1825,7 +1824,7 @@ together.</p></div>
 </dt>

 <dd>

 <p>

-        Overrides a previous --no-walk.

+        Overrides a previous <code>--no-walk</code>.

 </p>

 </dd>

 </dl></div>

@@ -1966,16 +1965,16 @@ 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 "--pretty". <code>log.date</code> config variable sets a default

-        value for log command&#8217;s --date option.

+        as when using <code>--pretty</code>. <code>log.date</code> config variable sets a default

+        value for the log command&#8217;s <code>--date</code> option.

 </p>

 <div class="paragraph"><p><code>--date=relative</code> shows dates relative to the current time,

-e.g. "2 hours ago".</p></div>

+e.g. &#8220;2 hours ago&#8221;.</p></div>

 <div class="paragraph"><p><code>--date=local</code> shows timestamps in user&#8217;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

-format, often found in E-mail messages.</p></div>

-<div class="paragraph"><p><code>--date=short</code> shows only date but not time, in <code>YYYY-MM-DD</code> format.</p></div>

+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

 (either committer&#8217;s or author&#8217;s).</p></div>

@@ -2058,8 +2057,8 @@ format, often found in E-mail 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 <em>--topo-order</em> option by default, but the

-<em>--date-order</em> option may also be specified.</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>

 </dd>

 <dt class="hdlist1">

 --count

@@ -2068,9 +2067,9 @@ format, often found in E-mail messages.</p></div>
 <p>

         Print a number stating how many commits would have been

         listed, and suppress all other output.  When used together

-        with <em>--left-right</em>, instead print the counts for left and

+        with <code>--left-right</code>, instead print the counts for left and

         right commits, separated by a tab. When used together with

-        <em>--cherry-mark</em>, omit patch equivalent commits from these

+        <code>--cherry-mark</code>, omit patch equivalent commits from these

         counts and print the count for equivalent commits separated

         by a tab.

 </p>