Autogenerated HTML docs for v1.5.6.1-89-gd544

diff --git a/RelNotes-1.5.4.6.txt b/RelNotes-1.5.4.6.txt
new file mode 100644 (file)
index 0000000..3e3c3e5
--- /dev/null
+++ b/RelNotes-1.5.4.6.txt
@@ -0,0 +1,43 @@
+GIT v1.5.4.6 Release Notes
+==========================
+
+I personally do not think there is any reason anybody should want to
+run v1.5.4.X series these days, because 'master' version is always
+more stable than any tagged released version of git.
+
+This is primarily to futureproof "git-shell" to accept requests
+without a dash between "git" and subcommand name (e.g. "git
+upload-pack") which the newer client will start to make sometime in
+the future.
+
+Fixes since v1.5.4.5
+--------------------
+
+ * Command line option "-n" to "git-repack" was not correctly parsed.
+
+ * Error messages from "git-apply" when the patchfile cannot be opened
+   have been improved.
+
+ * Error messages from "git-bisect" when given nonsense revisions have
+   been improved.
+
+ * reflog syntax that uses time e.g. "HEAD@{10 seconds ago}:path" did not
+   stop parsing at the closing "}".
+
+ * "git rev-parse --symbolic-full-name ^master^2" printed solitary "^",
+   but it should print nothing.
+
+ * "git apply" did not enforce "match at the beginning" correctly.
+
+ * a path specification "a/b" in .gitattributes file should not match
+   "sub/a/b", but it did.
+
+ * "git log --date-order --topo-order" did not override the earlier
+   date-order with topo-order as expected.
+
+ * "git fast-export" did not export octopus merges correctly.
+
+ * "git archive --prefix=$path/" mishandled gitattributes.
+
+As usual, it also comes with many documentation fixes and clarifications.
+

diff --git a/RelNotes-1.5.5.5.txt b/RelNotes-1.5.5.5.txt
new file mode 100644 (file)
index 0000000..30fa361
--- /dev/null
+++ b/RelNotes-1.5.5.5.txt
@@ -0,0 +1,11 @@
+GIT v1.5.5.5 Release Notes
+==========================
+
+I personally do not think there is any reason anybody should want to
+run v1.5.5.X series these days, because 'master' version is always
+more stable than any tagged released version of git.
+
+This is primarily to futureproof "git-shell" to accept requests
+without a dash between "git" and subcommand name (e.g. "git
+upload-pack") which the newer client will start to make sometime in
+the future.

diff --git a/gittutorial-2.html b/gittutorial-2.html
index 007cb0b10bd4c5f05e2e40011b030e75a82213e0..54c2c83e2c1c1c92ee7a7a243aa9d1479109ecc8 100644 (file)
--- a/gittutorial-2.html
+++ b/gittutorial-2.html
@@ -319,9 +319,9 @@ from your own version. Note that you can shorten it to only a few
 characters to save yourself typing all 40 hex digits:</p>\r
 <div class="listingblock">\r
 <div class="content">\r
-<pre><tt>$ git-cat-file -t 54196cc2\r
+<pre><tt>$ git cat-file -t 54196cc2\r
 commit\r
-$ git-cat-file commit 54196cc2\r
+$ git cat-file commit 54196cc2\r
 tree 92b8b694ffb1675e5975148e1121810081dbdffe\r
 author J. Bruce Fields &lt;bfields@puzzle.fieldses.org&gt; 1143414668 -0500\r
 committer J. Bruce Fields &lt;bfields@puzzle.fieldses.org&gt; 1143414668 -0500\r
@@ -414,7 +414,7 @@ hello world!</tt></pre>
 <p>and the "parent" object refers to the previous commit:</p>\r
 <div class="listingblock">\r
 <div class="content">\r
-<pre><tt>$ git-cat-file commit 54196cc2\r
+<pre><tt>$ git cat-file commit 54196cc2\r
 tree 92b8b694ffb1675e5975148e1121810081dbdffe\r
 author J. Bruce Fields &lt;bfields@puzzle.fieldses.org&gt; 1143414668 -0500\r
 committer J. Bruce Fields &lt;bfields@puzzle.fieldses.org&gt; 1143414668 -0500\r
@@ -504,7 +504,7 @@ $ git diff</tt></pre>
 head still doesn't contain the new line:</p>\r
 <div class="listingblock">\r
 <div class="content">\r
-<pre><tt>$ git-diff HEAD\r
+<pre><tt>$ git diff HEAD\r
 diff --git a/file.txt b/file.txt\r
 index a042389..513feba 100644\r
 --- a/file.txt\r
@@ -529,7 +529,7 @@ hello world, again</tt></pre>
 </div></div>\r
 <p>So what our "git add" did was store a new blob and then put\r
 a reference to it in the index file.  If we modify the file again,\r
-we'll see that the new modifications are reflected in the "git-diff"\r
+we'll see that the new modifications are reflected in the "git diff"\r
 output:</p>\r
 <div class="listingblock">\r
 <div class="content">\r
@@ -672,7 +672,7 @@ example, creating a new commit.</p>
 </div>\r
 <div id="footer">\r
 <div id="footer-text">\r
-Last updated 08-Jun-2008 01:34:29 UTC\r
+Last updated 27-Jun-2008 08:26:24 UTC\r
 </div>\r
 </div>\r
 </body>\r

diff --git a/gittutorial-2.txt b/gittutorial-2.txt
index e3d5c1fbf004760d4063352c2dd594e6b98b865f..31e8a23a4f3d9d842d950247ee4bd0c73c46e808 100644 (file)
--- a/gittutorial-2.txt
+++ b/gittutorial-2.txt
@@ -61,9 +61,9 @@ from your own version. Note that you can shorten it to only a few
 characters to save yourself typing all 40 hex digits:
 
 ------------------------------------------------
-$ git-cat-file -t 54196cc2
+$ git cat-file -t 54196cc2
 commit
-$ git-cat-file commit 54196cc2
+$ git cat-file commit 54196cc2
 tree 92b8b694ffb1675e5975148e1121810081dbdffe
 author J. Bruce Fields <bfields@puzzle.fieldses.org> 1143414668 -0500
 committer J. Bruce Fields <bfields@puzzle.fieldses.org> 1143414668 -0500
@@ -166,7 +166,7 @@ hello world!
 and the "parent" object refers to the previous commit:
 
 ------------------------------------------------
-$ git-cat-file commit 54196cc2
+$ git cat-file commit 54196cc2
 tree 92b8b694ffb1675e5975148e1121810081dbdffe
 author J. Bruce Fields <bfields@puzzle.fieldses.org> 1143414668 -0500
 committer J. Bruce Fields <bfields@puzzle.fieldses.org> 1143414668 -0500
@@ -246,7 +246,7 @@ The last diff is empty, but no new commits have been made, and the
 head still doesn't contain the new line:
 
 ------------------------------------------------
-$ git-diff HEAD
+$ git diff HEAD
 diff --git a/file.txt b/file.txt
 index a042389..513feba 100644
 --- a/file.txt
@@ -273,7 +273,7 @@ hello world, again
 
 So what our "git add" did was store a new blob and then put
 a reference to it in the index file.  If we modify the file again,
-we'll see that the new modifications are reflected in the "git-diff"
+we'll see that the new modifications are reflected in the "git diff"
 output:
 
 ------------------------------------------------