Autogenerated HTML docs for v1.5.3-rc4-29-g74276

diff --git a/git-commit.html b/git-commit.html
index 514f3d1baf88c44dd588055a37729b38d3c970d5..48283c0dd9ce456c0bf699a803b6dc2ebd35c20d 100644 (file)
--- a/git-commit.html
+++ b/git-commit.html
@@ -282,13 +282,17 @@ git-commit(1) Manual Page
 <div class="sectionbody">\r
 <p>Use <em>git commit</em> to store the current contents of the index in a new\r
 commit along with a log message describing the changes you have made.</p>\r
-<p>The content to be added can be specified in several ways:\r
-1. by using <a href="git-add.html">git-add(1)</a> to incrementally "add" changes to the\r
-   index before using the <em>commit</em> command (Note: even modified\r
-   files must be "added");</p>\r
+<p>The content to be added can be specified in several ways:</p>\r
 <ol>\r
 <li>\r
 <p>\r
+by using <a href="git-add.html">git-add(1)</a> to incrementally "add" changes to the\r
+   index before using the <em>commit</em> command (Note: even modified\r
+   files must be "added");\r
+</p>\r
+</li>\r
+<li>\r
+<p>\r
 by using <a href="git-rm.html">git-rm(1)</a> to remove files from the working tree\r
    and the index, again before using the <em>commit</em> command;\r
 </p>\r
@@ -697,7 +701,7 @@ Junio C Hamano &lt;junkio@cox.net&gt;</p>
 </div>\r
 <div id="footer">\r
 <div id="footer-text">\r
-Last updated 06-Aug-2007 06:42:07 UTC\r
+Last updated 08-Aug-2007 09:20:37 UTC\r
 </div>\r
 </div>\r
 </body>\r

diff --git a/git-commit.txt b/git-commit.txt
index 63599d382827e69341983a80d64d53dd18e9ac4e..e54fb12103d4e4955f41532566cb4558432a97bb 100644 (file)
--- a/git-commit.txt
+++ b/git-commit.txt
@@ -19,6 +19,7 @@ Use 'git commit' to store the current contents of the index in a new
 commit along with a log message describing the changes you have made.
 
 The content to be added can be specified in several ways:
+
 1. by using gitlink:git-add[1] to incrementally "add" changes to the
    index before using the 'commit' command (Note: even modified
    files must be "added");

diff --git a/git-stash.html b/git-stash.html
index fceecdd7206a1d9cdc53ee144a43cfbf4013f518..ec8f78fcc030f391f510aca6ad6a03e1ee0b4b3d 100644 (file)
--- a/git-stash.html
+++ b/git-stash.html
@@ -291,8 +291,8 @@ you can give a more descriptive message on the command line when
 you create one.</p>\r
 <p>The latest stash you created is stored in <tt>$GIT_DIR/refs/stash</tt>; older\r
 stashes are found in the reflog of this reference and can be named using\r
-the usual reflog syntax (e.g. <tt>stash@{1}</tt> is the most recently\r
-created stash, <tt>stash@{2}</tt> is the one before it, <tt>stash@{2.hours.ago}</tt>\r
+the usual reflog syntax (e.g. <tt>stash@{0}</tt> is the most recently\r
+created stash, <tt>stash@{1}</tt> is the one before it, <tt>stash@{2.hours.ago}</tt>\r
 is also possible).</p>\r
 </div>\r
 <h2>OPTIONS</h2>\r
@@ -314,7 +314,7 @@ list
 <dd>\r
 <p>\r
         List the stashes that you currently have.  Each <em>stash</em> is listed\r
-        with its name (e.g. <tt>stash@{0}</tt> is the latest stash, `stash@{1} is\r
+        with its name (e.g. <tt>stash@{0}</tt> is the latest stash, <tt>stash@{1}</tt> is\r
         the one before, etc.), the name of the branch that was current when the\r
         stash was made, and a short description of the commit the stash was\r
         based on.\r
@@ -334,7 +334,7 @@ show [&lt;stash&gt;]
         stashed state and its original parent. When no <tt>&lt;stash&gt;</tt> is given,\r
         shows the latest one. By default, the command shows the diffstat, but\r
         it will accept any format known to <tt>git-diff</tt> (e.g., <tt>git-stash show\r
-        -p stash@{2}</tt> to view the second most recent stash in patch form).\r
+        -p stash@{1}</tt> to view the second most recent stash in patch form).\r
 </p>\r
 </dd>\r
 <dt>\r
@@ -456,7 +456,7 @@ $ git stash apply
 </div>\r
 <div id="footer">\r
 <div id="footer-text">\r
-Last updated 19-Jul-2007 02:09:56 UTC\r
+Last updated 08-Aug-2007 09:20:37 UTC\r
 </div>\r
 </div>\r
 </body>\r

diff --git a/git-stash.txt b/git-stash.txt
index 17121ade56c317d974d537fa3aa3c2b5f116e502..05f40cff6cbaa9d8a08176a5a601b7e43d17e5bf 100644 (file)
--- a/git-stash.txt
+++ b/git-stash.txt
@@ -29,8 +29,8 @@ you create one.
 
 The latest stash you created is stored in `$GIT_DIR/refs/stash`; older
 stashes are found in the reflog of this reference and can be named using
-the usual reflog syntax (e.g. `stash@\{1}` is the most recently
-created stash, `stash@\{2}` is the one before it, `stash@\{2.hours.ago}`
+the usual reflog syntax (e.g. `stash@\{0}` is the most recently
+created stash, `stash@\{1}` is the one before it, `stash@\{2.hours.ago}`
 is also possible).
 
 OPTIONS
@@ -45,7 +45,7 @@ save::
 list::
 
        List the stashes that you currently have.  Each 'stash' is listed
-       with its name (e.g. `stash@\{0}` is the latest stash, `stash@\{1} is
+       with its name (e.g. `stash@\{0}` is the latest stash, `stash@\{1}` is
        the one before, etc.), the name of the branch that was current when the
        stash was made, and a short description of the commit the stash was
        based on.
@@ -61,7 +61,7 @@ show [<stash>]::
        stashed state and its original parent. When no `<stash>` is given,
        shows the latest one. By default, the command shows the diffstat, but
        it will accept any format known to `git-diff` (e.g., `git-stash show
-       -p stash@\{2}` to view the second most recent stash in patch form).
+       -p stash@\{1}` to view the second most recent stash in patch form).
 
 apply [<stash>]::
 

diff --git a/git-status.html b/git-status.html
index 51401ccd8aa8ec1ab6980c51fc9fc8f03cb994f5..821aa2b24eb8e306f9045417bcb9ddf01658f63a 100644 (file)
--- a/git-status.html
+++ b/git-status.html
@@ -288,6 +288,12 @@ status.</p>
 <p>The command takes the same set of options as <tt>git-commit</tt>; it\r
 shows what would be committed if the same options are given to\r
 <tt>git-commit</tt>.</p>\r
+<p>If any paths have been touched in the working tree (that is,\r
+their modification times have changed) but their contents and\r
+permissions are identical to those in the index file, the command\r
+updates the index file. Running <tt>git-status</tt> can thus speed up\r
+subsequent operations such as <tt>git-diff</tt> if the working tree\r
+contains many paths that have been touched but not modified.</p>\r
 </div>\r
 <h2>OUTPUT</h2>\r
 <div class="sectionbody">\r
@@ -320,7 +326,7 @@ Junio C Hamano &lt;junkio@cox.net&gt;.</p>
 </div>\r
 <div id="footer">\r
 <div id="footer-text">\r
-Last updated 19-Jul-2007 02:09:56 UTC\r
+Last updated 08-Aug-2007 09:20:38 UTC\r
 </div>\r
 </div>\r
 </body>\r

diff --git a/git-status.txt b/git-status.txt
index 6f16eb0328f754b5f5019ff5dac51604de7d535f..8fd0fc62368611bee25b4bbc3becef853937ff2c 100644 (file)
--- a/git-status.txt
+++ b/git-status.txt
@@ -27,6 +27,13 @@ The command takes the same set of options as `git-commit`; it
 shows what would be committed if the same options are given to
 `git-commit`.
 
+If any paths have been touched in the working tree (that is,
+their modification times have changed) but their contents and
+permissions are identical to those in the index file, the command
+updates the index file. Running `git-status` can thus speed up
+subsequent operations such as `git-diff` if the working tree
+contains many paths that have been touched but not modified.
+
 
 OUTPUT
 ------