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 5dff2a212d95219778bbdb2875c2241b872ba089..fea3f9935b7794ce86f04d22c9d68fb9d537167d 100644 (file)
--- 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 d74d76018bf20d83d5379e7f64003f927eabf025..1f4b79f3c90c37d0ae8578c912e666bed9980359 100644 (file)
--- a/git-commit-tree.html
+++ b/git-commit-tree.html
@@ -428,15 +428,15 @@ mind.</p>
   an warning if the commit log message given to it does not look\r
   like a valid UTF-8 string, unless you explicitly say your\r
   project uses a legacy encoding.  The way to say this is to\r
-  have core.commitencoding in <tt>.git/config</tt> file, like this:\r
+  have i18n.commitencoding in <tt>.git/config</tt> file, like this:\r
 </p>\r
 <div class="listingblock">\r
 <div class="content">\r
-<pre><tt>[core]\r
+<pre><tt>[i18n]\r
         commitencoding = ISO-8859-1</tt></pre>\r
 </div></div>\r
 <p>Commit objects created with the above setting record the value\r
-of <tt>core.commitencoding</tt> in its <tt>encoding</tt> header.  This is to\r
+of <tt>i18n.commitencoding</tt> in its <tt>encoding</tt> header.  This is to\r
 help other people who look at them later.  Lack of this header\r
 implies that the commit log message is encoded in UTF-8.</p>\r
 </li>\r
@@ -446,15 +446,15 @@ implies that the commit log message is encoded in UTF-8.</p>
   header of a commit object, and tries to re-code the log\r
   message into UTF-8 unless otherwise specified.  You can\r
   specify the desired output encoding with\r
-  <tt>core.logoutputencoding</tt> in <tt>.git/config</tt> file, like this:\r
+  <tt>i18n.logoutputencoding</tt> in <tt>.git/config</tt> file, like this:\r
 </p>\r
 <div class="listingblock">\r
 <div class="content">\r
-<pre><tt>[core]\r
+<pre><tt>[i18n]\r
         logoutputencoding = ISO-8859-1</tt></pre>\r
 </div></div>\r
 <p>If you do not have this configuration variable, the value of\r
-<tt>core.commitencoding</tt> is used instead.</p>\r
+<tt>i18n.commitencoding</tt> is used instead.</p>\r
 </li>\r
 </ol>\r
 <p>Note that we deliberately chose not to re-code the commit log\r
@@ -480,7 +480,7 @@ reversible operation.</p>
 </div>\r
 <div id="footer">\r
 <div id="footer-text">\r
-Last updated 19-Jan-2007 00:37:15 UTC\r
+Last updated 19-Feb-2007 05:35:40 UTC\r
 </div>\r
 </div>\r
 </body>\r

diff --git a/git-commit.html b/git-commit.html
index 0e22fcb6c5458b09f03c6aa8c2c579ec84ab6bbb..757de8dbcddc3e6f246d702f11b26d9debe08d38 100644 (file)
--- a/git-commit.html
+++ b/git-commit.html
@@ -592,15 +592,15 @@ mind.</p>
   an warning if the commit log message given to it does not look\r
   like a valid UTF-8 string, unless you explicitly say your\r
   project uses a legacy encoding.  The way to say this is to\r
-  have core.commitencoding in <tt>.git/config</tt> file, like this:\r
+  have i18n.commitencoding in <tt>.git/config</tt> file, like this:\r
 </p>\r
 <div class="listingblock">\r
 <div class="content">\r
-<pre><tt>[core]\r
+<pre><tt>[i18n]\r
         commitencoding = ISO-8859-1</tt></pre>\r
 </div></div>\r
 <p>Commit objects created with the above setting record the value\r
-of <tt>core.commitencoding</tt> in its <tt>encoding</tt> header.  This is to\r
+of <tt>i18n.commitencoding</tt> in its <tt>encoding</tt> header.  This is to\r
 help other people who look at them later.  Lack of this header\r
 implies that the commit log message is encoded in UTF-8.</p>\r
 </li>\r
@@ -610,15 +610,15 @@ implies that the commit log message is encoded in UTF-8.</p>
   header of a commit object, and tries to re-code the log\r
   message into UTF-8 unless otherwise specified.  You can\r
   specify the desired output encoding with\r
-  <tt>core.logoutputencoding</tt> in <tt>.git/config</tt> file, like this:\r
+  <tt>i18n.logoutputencoding</tt> in <tt>.git/config</tt> file, like this:\r
 </p>\r
 <div class="listingblock">\r
 <div class="content">\r
-<pre><tt>[core]\r
+<pre><tt>[i18n]\r
         logoutputencoding = ISO-8859-1</tt></pre>\r
 </div></div>\r
 <p>If you do not have this configuration variable, the value of\r
-<tt>core.commitencoding</tt> is used instead.</p>\r
+<tt>i18n.commitencoding</tt> is used instead.</p>\r
 </li>\r
 </ol>\r
 <p>Note that we deliberately chose not to re-code the commit log\r
@@ -656,7 +656,7 @@ Junio C Hamano &lt;junkio@cox.net&gt;</p>
 </div>\r
 <div id="footer">\r
 <div id="footer-text">\r
-Last updated 25-Jan-2007 02:23:45 UTC\r
+Last updated 19-Feb-2007 05:35:41 UTC\r
 </div>\r
 </div>\r
 </body>\r

diff --git a/git-log.html b/git-log.html
index 431cf4df0cf53ee1f2f6821be901c5929a134c65..5d60cedc4dd368f7ced987ed6cefc5c7d849b777 100644 (file)
--- a/git-log.html
+++ b/git-log.html
@@ -550,15 +550,15 @@ mind.</p>
   an warning if the commit log message given to it does not look\r
   like a valid UTF-8 string, unless you explicitly say your\r
   project uses a legacy encoding.  The way to say this is to\r
-  have core.commitencoding in <tt>.git/config</tt> file, like this:\r
+  have i18n.commitencoding in <tt>.git/config</tt> file, like this:\r
 </p>\r
 <div class="listingblock">\r
 <div class="content">\r
-<pre><tt>[core]\r
+<pre><tt>[i18n]\r
         commitencoding = ISO-8859-1</tt></pre>\r
 </div></div>\r
 <p>Commit objects created with the above setting record the value\r
-of <tt>core.commitencoding</tt> in its <tt>encoding</tt> header.  This is to\r
+of <tt>i18n.commitencoding</tt> in its <tt>encoding</tt> header.  This is to\r
 help other people who look at them later.  Lack of this header\r
 implies that the commit log message is encoded in UTF-8.</p>\r
 </li>\r
@@ -568,15 +568,15 @@ implies that the commit log message is encoded in UTF-8.</p>
   header of a commit object, and tries to re-code the log\r
   message into UTF-8 unless otherwise specified.  You can\r
   specify the desired output encoding with\r
-  <tt>core.logoutputencoding</tt> in <tt>.git/config</tt> file, like this:\r
+  <tt>i18n.logoutputencoding</tt> in <tt>.git/config</tt> file, like this:\r
 </p>\r
 <div class="listingblock">\r
 <div class="content">\r
-<pre><tt>[core]\r
+<pre><tt>[i18n]\r
         logoutputencoding = ISO-8859-1</tt></pre>\r
 </div></div>\r
 <p>If you do not have this configuration variable, the value of\r
-<tt>core.commitencoding</tt> is used instead.</p>\r
+<tt>i18n.commitencoding</tt> is used instead.</p>\r
 </li>\r
 </ol>\r
 <p>Note that we deliberately chose not to re-code the commit log\r
@@ -598,7 +598,7 @@ reversible operation.</p>
 </div>\r
 <div id="footer">\r
 <div id="footer-text">\r
-Last updated 09-Feb-2007 08:38:35 UTC\r
+Last updated 19-Feb-2007 05:35:41 UTC\r
 </div>\r
 </div>\r
 </body>\r

diff --git a/git-show.html b/git-show.html
index 48c4c0ef58c2e3a1556d98869623fc102a4e0a33..7dacc95df2a8b1f3a4c0fd41026acaa4438fd75d 100644 (file)
--- a/git-show.html
+++ b/git-show.html
@@ -515,15 +515,15 @@ mind.</p>
   an warning if the commit log message given to it does not look\r
   like a valid UTF-8 string, unless you explicitly say your\r
   project uses a legacy encoding.  The way to say this is to\r
-  have core.commitencoding in <tt>.git/config</tt> file, like this:\r
+  have i18n.commitencoding in <tt>.git/config</tt> file, like this:\r
 </p>\r
 <div class="listingblock">\r
 <div class="content">\r
-<pre><tt>[core]\r
+<pre><tt>[i18n]\r
         commitencoding = ISO-8859-1</tt></pre>\r
 </div></div>\r
 <p>Commit objects created with the above setting record the value\r
-of <tt>core.commitencoding</tt> in its <tt>encoding</tt> header.  This is to\r
+of <tt>i18n.commitencoding</tt> in its <tt>encoding</tt> header.  This is to\r
 help other people who look at them later.  Lack of this header\r
 implies that the commit log message is encoded in UTF-8.</p>\r
 </li>\r
@@ -533,15 +533,15 @@ implies that the commit log message is encoded in UTF-8.</p>
   header of a commit object, and tries to re-code the log\r
   message into UTF-8 unless otherwise specified.  You can\r
   specify the desired output encoding with\r
-  <tt>core.logoutputencoding</tt> in <tt>.git/config</tt> file, like this:\r
+  <tt>i18n.logoutputencoding</tt> in <tt>.git/config</tt> file, like this:\r
 </p>\r
 <div class="listingblock">\r
 <div class="content">\r
-<pre><tt>[core]\r
+<pre><tt>[i18n]\r
         logoutputencoding = ISO-8859-1</tt></pre>\r
 </div></div>\r
 <p>If you do not have this configuration variable, the value of\r
-<tt>core.commitencoding</tt> is used instead.</p>\r
+<tt>i18n.commitencoding</tt> is used instead.</p>\r
 </li>\r
 </ol>\r
 <p>Note that we deliberately chose not to re-code the commit log\r
@@ -566,7 +566,7 @@ Johannes Schindelin &lt;Johannes.Schindelin@gmx.de&gt;.</p>
 </div>\r
 <div id="footer">\r
 <div id="footer-text">\r
-Last updated 09-Feb-2007 08:38:37 UTC\r
+Last updated 19-Feb-2007 05:35:42 UTC\r
 </div>\r
 </div>\r
 </body>\r

diff --git a/i18n.txt b/i18n.txt
index b4cbb3830e83cd488936b53687aa6ec92bf4352a..b95f99be6c34ccb7e8583a68d1b1c75a1bf653ca 100644 (file)
--- 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