From: Junio C Hamano Date: Mon, 19 Feb 2007 05:35:53 +0000 (+0000) Subject: Autogenerated HTML docs for v1.5.0.1-26-gf5a92 X-Git-Url: http://git.tremily.us/?a=commitdiff_plain;h=35bb3f600bc6a09085ad895e86a1ffdf6370407a;p=git.git Autogenerated HTML docs for v1.5.0.1-26-gf5a92 --- diff --git a/RelNotes-1.5.0.1.txt b/RelNotes-1.5.0.1.txt index 5dff2a212..fea3f9935 100644 --- a/RelNotes-1.5.0.1.txt +++ b/RelNotes-1.5.0.1.txt @@ -15,8 +15,16 @@ Fixes since v1.5.0 - Converted remaining mentions of update-index on Porcelain documents to git-add/git-rm. + - Some i18n.* configuration variables were incorrectly + described as core.*; fixed. + * Bugfixes + - git-add and git-update-index on a filesystem on which + executable bits are unreliable incorrectly reused st_mode + bits even when the path changed between symlink and regular + file. + - git-daemon marks the listening sockets with FD_CLOEXEC so that it won't be leaked into the children. @@ -24,14 +32,11 @@ Fixes since v1.5.0 parameter was missing was fixed; usage() message is given instead. + - git-rev-list did not read $GIT_DIR/config file, which means + that did not honor i18n.logoutputencoding correctly. + * Tweaks - sliding mmap() inefficiently mmaped the same region of a packfile with an access pattern that used objects in the reverse order. This has been made more efficient. - --- -exec >/var/tmp/1 -O=v1.5.0-24-g460ca30 -echo O=`git describe maint` -git shortlog --no-merges $O..maint diff --git a/git-commit-tree.html b/git-commit-tree.html index d74d76018..1f4b79f3c 100644 --- a/git-commit-tree.html +++ b/git-commit-tree.html @@ -428,15 +428,15 @@ mind.

an 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 core.commitencoding in .git/config file, like this: + have i18n.commitencoding in .git/config file, like this:

-
[core]
+
[i18n]
         commitencoding = ISO-8859-1

Commit objects created with the above setting record the value -of core.commitencoding in its encoding header. This is to +of i18n.commitencoding in its encoding header. This is to help other people who look at them later. Lack of this header implies that the commit log message is encoded in UTF-8.

@@ -446,15 +446,15 @@ implies that the commit log message is encoded in UTF-8.

header of a commit object, and tries to re-code the log message into UTF-8 unless otherwise specified. You can specify the desired output encoding with - core.logoutputencoding in .git/config file, like this: + i18n.logoutputencoding in .git/config file, like this:

-
[core]
+
[i18n]
         logoutputencoding = ISO-8859-1

If you do not have this configuration variable, the value of -core.commitencoding is used instead.

+i18n.commitencoding is used instead.

Note that we deliberately chose not to re-code the commit log @@ -480,7 +480,7 @@ reversible operation.

diff --git a/git-commit.html b/git-commit.html index 0e22fcb6c..757de8dbc 100644 --- a/git-commit.html +++ b/git-commit.html @@ -592,15 +592,15 @@ mind.

an 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 core.commitencoding in .git/config file, like this: + have i18n.commitencoding in .git/config file, like this:

-
[core]
+
[i18n]
         commitencoding = ISO-8859-1

Commit objects created with the above setting record the value -of core.commitencoding in its encoding header. This is to +of i18n.commitencoding in its encoding header. This is to help other people who look at them later. Lack of this header implies that the commit log message is encoded in UTF-8.

@@ -610,15 +610,15 @@ implies that the commit log message is encoded in UTF-8.

header of a commit object, and tries to re-code the log message into UTF-8 unless otherwise specified. You can specify the desired output encoding with - core.logoutputencoding in .git/config file, like this: + i18n.logoutputencoding in .git/config file, like this:

-
[core]
+
[i18n]
         logoutputencoding = ISO-8859-1

If you do not have this configuration variable, the value of -core.commitencoding is used instead.

+i18n.commitencoding is used instead.

Note that we deliberately chose not to re-code the commit log @@ -656,7 +656,7 @@ Junio C Hamano <junkio@cox.net>

diff --git a/git-log.html b/git-log.html index 431cf4df0..5d60cedc4 100644 --- a/git-log.html +++ b/git-log.html @@ -550,15 +550,15 @@ mind.

an 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 core.commitencoding in .git/config file, like this: + have i18n.commitencoding in .git/config file, like this:

-
[core]
+
[i18n]
         commitencoding = ISO-8859-1

Commit objects created with the above setting record the value -of core.commitencoding in its encoding header. This is to +of i18n.commitencoding in its encoding header. This is to help other people who look at them later. Lack of this header implies that the commit log message is encoded in UTF-8.

@@ -568,15 +568,15 @@ implies that the commit log message is encoded in UTF-8.

header of a commit object, and tries to re-code the log message into UTF-8 unless otherwise specified. You can specify the desired output encoding with - core.logoutputencoding in .git/config file, like this: + i18n.logoutputencoding in .git/config file, like this:

-
[core]
+
[i18n]
         logoutputencoding = ISO-8859-1

If you do not have this configuration variable, the value of -core.commitencoding is used instead.

+i18n.commitencoding is used instead.

Note that we deliberately chose not to re-code the commit log @@ -598,7 +598,7 @@ reversible operation.

diff --git a/git-show.html b/git-show.html index 48c4c0ef5..7dacc95df 100644 --- a/git-show.html +++ b/git-show.html @@ -515,15 +515,15 @@ mind.

an 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 core.commitencoding in .git/config file, like this: + have i18n.commitencoding in .git/config file, like this:

-
[core]
+
[i18n]
         commitencoding = ISO-8859-1

Commit objects created with the above setting record the value -of core.commitencoding in its encoding header. This is to +of i18n.commitencoding in its encoding header. This is to help other people who look at them later. Lack of this header implies that the commit log message is encoded in UTF-8.

@@ -533,15 +533,15 @@ implies that the commit log message is encoded in UTF-8.

header of a commit object, and tries to re-code the log message into UTF-8 unless otherwise specified. You can specify the desired output encoding with - core.logoutputencoding in .git/config file, like this: + i18n.logoutputencoding in .git/config file, like this:

-
[core]
+
[i18n]
         logoutputencoding = ISO-8859-1

If you do not have this configuration variable, the value of -core.commitencoding is used instead.

+i18n.commitencoding is used instead.

Note that we deliberately chose not to re-code the commit log @@ -566,7 +566,7 @@ Johannes Schindelin <Johannes.Schindelin@gmx.de>.

diff --git a/i18n.txt b/i18n.txt index b4cbb3830..b95f99be6 100644 --- a/i18n.txt +++ b/i18n.txt @@ -25,15 +25,15 @@ mind. an 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 core.commitencoding in `.git/config` file, like this: + have i18n.commitencoding in `.git/config` file, like this: + ------------ -[core] +[i18n] commitencoding = ISO-8859-1 ------------ + Commit objects created with the above setting record the value -of `core.commitencoding` in its `encoding` header. This is to +of `i18n.commitencoding` in its `encoding` header. This is to help other people who look at them later. Lack of this header implies that the commit log message is encoded in UTF-8. @@ -41,15 +41,15 @@ implies that the commit log message is encoded in UTF-8. header of a commit object, and tries to re-code the log message into UTF-8 unless otherwise specified. You can specify the desired output encoding with - `core.logoutputencoding` in `.git/config` file, like this: + `i18n.logoutputencoding` in `.git/config` file, like this: + ------------ -[core] +[i18n] logoutputencoding = ISO-8859-1 ------------ + If you do not have this configuration variable, the value of -`core.commitencoding` is used instead. +`i18n.commitencoding` is used instead. Note that we deliberately chose not to re-code the commit log message when a commit is made to force UTF-8 at the commit