From 432d8ee687912ee33b1b18ab27b6407a2b3f9c3d Mon Sep 17 00:00:00 2001 From: Junio C Hamano Date: Fri, 27 Jun 2008 08:26:43 +0000 Subject: [PATCH] Autogenerated HTML docs for v1.5.6.1-89-gd544 --- RelNotes-1.5.4.6.txt | 43 +++++++++++++++++++++++++++++++++++++++++++ RelNotes-1.5.5.5.txt | 11 +++++++++++ gittutorial-2.html | 12 ++++++------ gittutorial-2.txt | 10 +++++----- 4 files changed, 65 insertions(+), 11 deletions(-) create mode 100644 RelNotes-1.5.4.6.txt create mode 100644 RelNotes-1.5.5.5.txt diff --git a/RelNotes-1.5.4.6.txt b/RelNotes-1.5.4.6.txt new file mode 100644 index 000000000..3e3c3e55a --- /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 index 000000000..30fa3615c --- /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 007cb0b10..54c2c83e2 100644 --- 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:

-
$ 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
@@ -414,7 +414,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
@@ -504,7 +504,7 @@ $ git diff

 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
@@ -529,7 +529,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:

 

 

@@ -672,7 +672,7 @@ example, creating a new commit.

 

 
 
diff --git a/gittutorial-2.txt b/gittutorial-2.txt
index e3d5c1fbf..31e8a23a4 100644
--- 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  1143414668 -0500
 committer J. Bruce Fields  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  1143414668 -0500
 committer J. Bruce Fields  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:
 
 ------------------------------------------------
-- 
2.26.2