Autogenerated HTML docs for v1.5.4-rc2-38-gd6da3

diff --git a/RelNotes-1.5.4.txt b/RelNotes-1.5.4.txt
index e6fbcdb2e17b061163ddb0f8c218a395480ea572..c6953ea5153c77629734570f151aba01e65b4e8f 100644 (file)
--- a/RelNotes-1.5.4.txt
+++ b/RelNotes-1.5.4.txt
@@ -114,6 +114,9 @@ Updates since v1.5.3
 
  * "git reset" is now built-in and its output can be squelched with -q.
 
+ * "git reset --hard" does not make any sense in a bare
+   repository, but did not error out; fixed.
+
  * "git send-email" can optionally talk over ssmtp and use SMTP-AUTH.
 
  * "git rebase" learned --whitespace option.
@@ -344,6 +347,6 @@ series.
 
 --
 exec >/var/tmp/1
-O=v1.5.4-rc1-36-g49e6be5
+O=v1.5.4-rc2-37-ge0cd252
 echo O=`git describe refs/heads/master`
 git shortlog --no-merges $O..refs/heads/master ^refs/heads/maint

diff --git a/git-commit-tree.html b/git-commit-tree.html
index cea81645b262020c366c59c43787e95286e79390..3d5adcafbc672e3f1a202dfba4d46ed05b2fdb6b 100644 (file)
--- a/git-commit-tree.html
+++ b/git-commit-tree.html
@@ -422,7 +422,7 @@ mind.</p>
 <li>\r
 <p>\r
 <tt>git-commit-tree</tt> (hence, <tt>git-commit</tt> which uses it) issues\r
-  an warning if the commit log message given to it does not look\r
+  a warning if the commit log message given to it does not look\r
   like a valid UTF-8 string, unless you explicitly say your\r
   project uses a legacy encoding.  The way to say this is to\r
   have i18n.commitencoding in <tt>.git/config</tt> file, like this:\r
@@ -477,7 +477,7 @@ reversible operation.</p>
 </div>\r
 <div id="footer">\r
 <div id="footer-text">\r
-Last updated 14-Nov-2007 12:11:24 UTC\r
+Last updated 05-Jan-2008 10:31:57 UTC\r
 </div>\r
 </div>\r
 </body>\r

diff --git a/git-commit.html b/git-commit.html
index d0a6bbea50d926b5205491b4859a30c5773e877a..601a162e3987eb8a2ca554fd687f4d3ccee1c240 100644 (file)
--- a/git-commit.html
+++ b/git-commit.html
@@ -661,7 +661,7 @@ mind.</p>
 <li>\r
 <p>\r
 <tt>git-commit-tree</tt> (hence, <tt>git-commit</tt> which uses it) issues\r
-  an warning if the commit log message given to it does not look\r
+  a warning if the commit log message given to it does not look\r
   like a valid UTF-8 string, unless you explicitly say your\r
   project uses a legacy encoding.  The way to say this is to\r
   have i18n.commitencoding in <tt>.git/config</tt> file, like this:\r
@@ -730,7 +730,7 @@ Junio C Hamano &lt;junkio@cox.net&gt;</p>
 </div>\r
 <div id="footer">\r
 <div id="footer-text">\r
-Last updated 27-Dec-2007 03:28:36 UTC\r
+Last updated 05-Jan-2008 10:31:57 UTC\r
 </div>\r
 </div>\r
 </body>\r

diff --git a/git-log.html b/git-log.html
index fc59725ef858c9040113d554c19f6448fa849e7c..1c32e39e939677eb00e27c73900065713707f815 100644 (file)
--- a/git-log.html
+++ b/git-log.html
@@ -1426,7 +1426,7 @@ mind.</p>
 <li>\r
 <p>\r
 <tt>git-commit-tree</tt> (hence, <tt>git-commit</tt> which uses it) issues\r
-  an warning if the commit log message given to it does not look\r
+  a warning if the commit log message given to it does not look\r
   like a valid UTF-8 string, unless you explicitly say your\r
   project uses a legacy encoding.  The way to say this is to\r
   have i18n.commitencoding in <tt>.git/config</tt> file, like this:\r
@@ -1477,7 +1477,7 @@ reversible operation.</p>
 </div>\r
 <div id="footer">\r
 <div id="footer-text">\r
-Last updated 27-Dec-2007 03:28:36 UTC\r
+Last updated 05-Jan-2008 10:31:57 UTC\r
 </div>\r
 </div>\r
 </body>\r

diff --git a/git-reset.html b/git-reset.html
index 368914a72b2b99e3198cf3bd0383db91ee58e0d0..3be0caf00a9963f56febd6aaeb6a924bf29b19d3 100644 (file)
--- a/git-reset.html
+++ b/git-reset.html
@@ -274,7 +274,7 @@ git-reset(1) Manual Page
 <div class="sectionbody">\r
 <div class="verseblock">\r
 <div class="content"><em>git-reset</em> [--mixed | --soft | --hard] [-q] [&lt;commit&gt;]\r
-<em>git-reset</em> [--mixed] [-q] &lt;commit&gt; [--] &lt;paths&gt;&#8230;</div></div>\r
+<em>git-reset</em> [--mixed] [-q] [&lt;commit&gt;] [--] &lt;paths&gt;&#8230;</div></div>\r
 </div>\r
 <h2>DESCRIPTION</h2>\r
 <div class="sectionbody">\r
@@ -335,7 +335,7 @@ the index from a given commit, without moving HEAD.</p>
 </dt>\r
 <dd>\r
 <p>\r
-        Commit to make the current HEAD.\r
+        Commit to make the current HEAD. If not given defaults to HEAD.\r
 </p>\r
 </dd>\r
 </dl>\r
@@ -575,7 +575,7 @@ At this point the index file still has all the WIP changes you
 </div>\r
 <div id="footer">\r
 <div id="footer-text">\r
-Last updated 14-Nov-2007 12:11:45 UTC\r
+Last updated 05-Jan-2008 10:31:57 UTC\r
 </div>\r
 </div>\r
 </body>\r

diff --git a/git-reset.txt b/git-reset.txt
index 050e4eadbb3d5b8f60edc173f2f17fdc959dde5d..69722d14d34a3f9de9d94ec7b48ae85995ce8625 100644 (file)
--- a/git-reset.txt
+++ b/git-reset.txt
@@ -9,7 +9,7 @@ SYNOPSIS
 --------
 [verse]
 'git-reset' [--mixed | --soft | --hard] [-q] [<commit>]
-'git-reset' [--mixed] [-q] <commit> [--] <paths>...
+'git-reset' [--mixed] [-q] [<commit>] [--] <paths>...
 
 DESCRIPTION
 -----------
@@ -49,7 +49,7 @@ OPTIONS
        Be quiet, only report errors.
 
 <commit>::
-       Commit to make the current HEAD.
+       Commit to make the current HEAD. If not given defaults to HEAD.
 
 Examples
 --------

diff --git a/git-show.html b/git-show.html
index 1e0834b2de92471c91a2a8c4784277d47c23e748..0c1afc56fcb80d6c76ec249d690b750ed24a2cad 100644 (file)
--- a/git-show.html
+++ b/git-show.html
@@ -708,7 +708,7 @@ mind.</p>
 <li>\r
 <p>\r
 <tt>git-commit-tree</tt> (hence, <tt>git-commit</tt> which uses it) issues\r
-  an warning if the commit log message given to it does not look\r
+  a warning if the commit log message given to it does not look\r
   like a valid UTF-8 string, unless you explicitly say your\r
   project uses a legacy encoding.  The way to say this is to\r
   have i18n.commitencoding in <tt>.git/config</tt> file, like this:\r
@@ -762,7 +762,7 @@ Johannes Schindelin &lt;Johannes.Schindelin@gmx.de&gt;.</p>
 </div>\r
 <div id="footer">\r
 <div id="footer-text">\r
-Last updated 14-Nov-2007 12:11:50 UTC\r
+Last updated 05-Jan-2008 10:31:58 UTC\r
 </div>\r
 </div>\r
 </body>\r

diff --git a/i18n.txt b/i18n.txt
index b95f99be6c34ccb7e8583a68d1b1c75a1bf653ca..1e188e6e742d06056fcd8eafd89c13ef36685d4e 100644 (file)
--- a/i18n.txt
+++ b/i18n.txt
@@ -22,7 +22,7 @@ does not forbid it.  However, there are a few things to keep in
 mind.
 
 . `git-commit-tree` (hence, `git-commit` which uses it) issues
-  an warning if the commit log message given to it does not look
+  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 `.git/config` file, like this: