Autogenerated HTML docs for v1.8.1.2-545-g2f19ad

1 files changed, 10 insertions, 10 deletions

diff --git a/git-log.html b/git-log.html
index 37beb06fd..c87241fae 100644
--- a/git-log.html
+++ b/git-log.html
@@ -840,7 +840,7 @@ produced by --stat etc.</p></div>
 <dd>

 <p>

         Before the log message print out its size in bytes. Intended

-        mainly for porcelain tools consumption. If git is unable to

+        mainly for porcelain tools consumption. If Git is unable to

         produce a valid value size is set to zero.

         Note that only message is considered, if also a diff is shown

         its size is not included.

@@ -1686,7 +1686,7 @@ together.</p></div>
 </div>

 <div class="sect2">

 <h3 id="_object_traversal">Object Traversal</h3>

-<div class="paragraph"><p>These options are mostly targeted for packing of git repositories.</p></div>

+<div class="paragraph"><p>These options are mostly targeted for packing of Git repositories.</p></div>

 <div class="dlist"><dl>

 <dt class="hdlist1">

 --objects

@@ -1886,7 +1886,7 @@ e.g. "2 hours ago".</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>

-<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=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 timezone

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

 </dd>

@@ -2931,7 +2931,7 @@ 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

-original should remain in the result for git to consider it a total

+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

@@ -2955,7 +2955,7 @@ another file.</p></div>
         <code>--follow</code>.

         If <code>n</code> is specified, it is a threshold on the similarity

         index (i.e. amount of addition/deletions compared to the

-        file&#8217;s size). For example, <code>-M90%</code> means git should consider a

+        file&#8217;s size). For example, <code>-M90%</code> means Git should consider a

         delete/add pair to be a rename if more than 90% of the file

         hasn&#8217;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

@@ -3566,14 +3566,14 @@ two unresolved merge parents with the working tree file
 <div class="sect1">

 <h2 id="_discussion">Discussion</h2>

 <div class="sectionbody">

-<div class="paragraph"><p>At the core level, git is character encoding agnostic.</p></div>

+<div class="paragraph"><p>At the core level, Git is character encoding agnostic.</p></div>

 <div class="ulist"><ul>

 <li>

 <p>

 The pathnames recorded in the index and in the tree objects

    are treated as uninterpreted sequences of non-NUL bytes.

    What readdir(2) returns are what are recorded and compared

-   with the data git keeps track of, which in turn are expected

+   with the data Git keeps track of, which in turn are expected

    to be what lstat(2) and creat(2) accepts.  There is no such

    thing as pathname encoding translation.

 </p>

@@ -3593,9 +3593,9 @@ The commit log messages are uninterpreted sequences of non-NUL
 </li>

 </ul></div>

 <div class="paragraph"><p>Although we encourage that the commit log messages are encoded

-in UTF-8, both the core and git Porcelain are designed not to

+in UTF-8, both the core and Git Porcelain are designed not to

 force UTF-8 on projects.  If all participants of a particular

-project find it more convenient to use legacy encodings, git

+project find it more convenient to use legacy encodings, Git

 does not forbid it.  However, there are a few things to keep in

 mind.</p></div>

 <div class="olist arabic"><ol class="arabic">

@@ -3724,7 +3724,7 @@ and overridden by the <code>--notes=&lt;ref&gt;</code> option.</p></div>
 <div id="footnotes"><hr /></div>

 <div id="footer">

 <div id="footer-text">

-Last updated 2013-01-20 18:01:21 PST

+Last updated 2013-02-05 21:07:26 PST

 </div>

 </div>

 </body>