Autogenerated HTML docs for v1.5.5-40-g4cdda

diff --git a/git-bisect.html b/git-bisect.html
index 5df54707e0fb4ab147f9f3c46e820d1ddf4ed0c1..4389791624d2f5e95b8035397c07ca3ab6e54721 100644 (file)
--- a/git-bisect.html
+++ b/git-bisect.html
@@ -280,7 +280,8 @@ git-bisect(1) Manual Page
 on the subcommand:</p>\r
 <div class="literalblock">\r
 <div class="content">\r
-<pre><tt>git bisect start [&lt;bad&gt; [&lt;good&gt;...]] [--] [&lt;paths&gt;...]\r
+<pre><tt>git bisect help\r
+git bisect start [&lt;bad&gt; [&lt;good&gt;...]] [--] [&lt;paths&gt;...]\r
 git bisect bad [&lt;rev&gt;]\r
 git bisect good [&lt;rev&gt;...]\r
 git bisect skip [&lt;rev&gt;...]\r
@@ -293,6 +294,9 @@ git bisect run &lt;cmd&gt;...</tt></pre>
 <p>This command uses <em>git-rev-list --bisect</em> option to help drive the\r
 binary search process to find which change introduced a bug, given an\r
 old "good" commit object name and a later "bad" commit object name.</p>\r
+<h3>Getting help</h3>\r
+<p>Use "git bisect" to get a short usage description, and "git bisect\r
+help" or "git bisect -h" to get a long usage description.</p>\r
 <h3>Basic bisect commands: start, bad, good</h3>\r
 <p>The way you use it is:</p>\r
 <div class="listingblock">\r
@@ -453,7 +457,7 @@ know the outcome.</p>
 </div>\r
 <div id="footer">\r
 <div id="footer-text">\r
-Last updated 07-Jan-2008 07:50:02 UTC\r
+Last updated 12-Apr-2008 08:22:49 UTC\r
 </div>\r
 </div>\r
 </body>\r

diff --git a/git-bisect.txt b/git-bisect.txt
index 96585ae8d9455654b63e83d61e7c34a7aeb94291..698ffde7ce844e38abe2719b2f8043783742f134 100644 (file)
--- a/git-bisect.txt
+++ b/git-bisect.txt
@@ -15,6 +15,7 @@ DESCRIPTION
 The command takes various subcommands, and different options depending
 on the subcommand:
 
+ git bisect help
  git bisect start [<bad> [<good>...]] [--] [<paths>...]
  git bisect bad [<rev>]
  git bisect good [<rev>...]
@@ -29,6 +30,12 @@ This command uses 'git-rev-list --bisect' option to help drive the
 binary search process to find which change introduced a bug, given an
 old "good" commit object name and a later "bad" commit object name.
 
+Getting help
+~~~~~~~~~~~~
+
+Use "git bisect" to get a short usage description, and "git bisect
+help" or "git bisect -h" to get a long usage description.
+
 Basic bisect commands: start, bad, good
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 

diff --git a/git-commit.html b/git-commit.html
index 5e7e4aaf0849b0e2cfe4d5bcff9dbf7e3ed6afa6..0b1c56969f4b13a94d6ff33b5519f387848fd6dd 100644 (file)
--- a/git-commit.html
+++ b/git-commit.html
@@ -481,6 +481,22 @@ that, you can recover from it with <a href="git-reset.html">git-reset(1)</a>.</p
 </p>\r
 </dd>\r
 <dt>\r
+-o|--only\r
+</dt>\r
+<dd>\r
+<p>\r
+        Make a commit only from the paths specified on the\r
+        command line, disregarding any contents that have been\r
+        staged so far. This is the default mode of operation of\r
+        <em>git commit</em> if any paths are given on the command line,\r
+        in which case this option can be omitted.\r
+        If this option is specified together with <em>--amend</em>, then\r
+        no paths need be specified, which can be used to amend\r
+        the last commit without committing changes that have\r
+        already been staged.\r
+</p>\r
+</dd>\r
+<dt>\r
 -u|--untracked-files\r
 </dt>\r
 <dd>\r
@@ -730,7 +746,7 @@ Junio C Hamano &lt;junkio@cox.net&gt;</p>
 </div>\r
 <div id="footer">\r
 <div id="footer-text">\r
-Last updated 17-Feb-2008 03:50:04 UTC\r
+Last updated 12-Apr-2008 08:22:49 UTC\r
 </div>\r
 </div>\r
 </body>\r

diff --git a/git-commit.txt b/git-commit.txt
index b4ae61ff46f4b7ff9e71e9e91a999fdc8fc17560..4bb51cc06ec5e1f47b748b14353e49a0acfdc775 100644 (file)
--- a/git-commit.txt
+++ b/git-commit.txt
@@ -139,6 +139,17 @@ but can be used to amend a merge commit.
        as well.  This is usually not what you want unless you
        are concluding a conflicted merge.
 
+-o|--only::
+       Make a commit only from the paths specified on the
+       command line, disregarding any contents that have been
+       staged so far. This is the default mode of operation of
+       'git commit' if any paths are given on the command line,
+       in which case this option can be omitted.
+       If this option is specified together with '--amend', then
+       no paths need be specified, which can be used to amend
+       the last commit without committing changes that have
+       already been staged.
+
 -u|--untracked-files::
        Show all untracked files, also those in uninteresting
        directories, in the "Untracked files:" section of commit

diff --git a/git-request-pull.html b/git-request-pull.html
index f6b71a97034ca00284ab308f39894f80ba67d904..1ad2fe5df26a14e6f82d47e7756e9d0d6cdb8eca 100644 (file)
--- a/git-request-pull.html
+++ b/git-request-pull.html
@@ -303,7 +303,7 @@ the given URL in the generated summary.</p>
 </dt>\r
 <dd>\r
 <p>\r
-        Commit to send at; defaults to HEAD.\r
+        Commit to end at; defaults to HEAD.\r
 </p>\r
 </dd>\r
 </dl>\r
@@ -322,7 +322,7 @@ the given URL in the generated summary.</p>
 </div>\r
 <div id="footer">\r
 <div id="footer-text">\r
-Last updated 07-Jan-2008 07:50:42 UTC\r
+Last updated 12-Apr-2008 08:22:50 UTC\r
 </div>\r
 </div>\r
 </body>\r

diff --git a/git-request-pull.txt b/git-request-pull.txt
index 270df9b185a53977665c2143bdffa6f3c275d326..9a14c04e39bd6c5c41de988f7dd9d18477e92c85 100644 (file)
--- a/git-request-pull.txt
+++ b/git-request-pull.txt
@@ -24,7 +24,7 @@ OPTIONS
        URL to include in the summary.
 
 <end>::
-       Commit to send at; defaults to HEAD.
+       Commit to end at; defaults to HEAD.
 
 Author
 ------

diff --git a/git-tag.html b/git-tag.html
index 09564a095617214fbb40351c0a489ae3b3deebb1..77ff1c5a8cdc5394d7bcb0ad5502e19410220c0e 100644 (file)
--- a/git-tag.html
+++ b/git-tag.html
@@ -528,13 +528,13 @@ to specify the date to embed inside of the tag object.  The data in
 the tag object affects, for example, the ordering of tags in the\r
 gitweb interface.</p>\r
 <p>To set the date used in future tag objects, set the environment\r
-variable GIT_AUTHOR_DATE to one or more of the date and time.  The\r
+variable GIT_COMMITTER_DATE to one or more of the date and time.  The\r
 date and time can be specified in a number of ways; the most common\r
 is "YYYY-MM-DD HH:MM".</p>\r
 <p>An example follows.</p>\r
 <div class="listingblock">\r
 <div class="content">\r
-<pre><tt>$ GIT_AUTHOR_DATE="2006-10-02 10:31" git tag -s v1.0.1</tt></pre>\r
+<pre><tt>$ GIT_COMMITTER_DATE="2006-10-02 10:31" git tag -s v1.0.1</tt></pre>\r
 </div></div>\r
 </div>\r
 <h2>Author</h2>\r
@@ -552,7 +552,7 @@ Junio C Hamano &lt;junkio@cox.net&gt; and Chris Wright &lt;chrisw@osdl.org&gt;.<
 </div>\r
 <div id="footer">\r
 <div id="footer-text">\r
-Last updated 11-Apr-2008 05:28:27 UTC\r
+Last updated 12-Apr-2008 08:22:50 UTC\r
 </div>\r
 </div>\r
 </body>\r

diff --git a/git-tag.txt b/git-tag.txt
index 4b6fd90eafbcb9834a4b3bf733fef28b3f895fde..9712392f7946366129056ed8a0b7b8fab83c0ed5 100644 (file)
--- a/git-tag.txt
+++ b/git-tag.txt
@@ -233,14 +233,14 @@ the tag object affects, for example, the ordering of tags in the
 gitweb interface.
 
 To set the date used in future tag objects, set the environment
-variable GIT_AUTHOR_DATE to one or more of the date and time.  The
+variable GIT_COMMITTER_DATE to one or more of the date and time.  The
 date and time can be specified in a number of ways; the most common
 is "YYYY-MM-DD HH:MM".
 
 An example follows.
 
 ------------
-$ GIT_AUTHOR_DATE="2006-10-02 10:31" git tag -s v1.0.1
+$ GIT_COMMITTER_DATE="2006-10-02 10:31" git tag -s v1.0.1
 ------------