Autogenerated man pages for v1.5.0.1-26-gf5a92

diff --git a/man1/git-commit-tree.1 b/man1/git-commit-tree.1
index 4d125b5857750cb09b4779431ff001fca7b309f7..f52ac81459e4be72ced12d436b3630ab279f56e4 100644 (file)
--- a/man1/git-commit-tree.1
+++ b/man1/git-commit-tree.1
@@ -2,7 +2,7 @@
 .\" It was generated using the DocBook XSL Stylesheets (version 1.69.1).
 .\" Instead of manually editing it, you probably should edit the DocBook XML
 .\" source for it and then use the DocBook XSL Stylesheets to regenerate it.
-.TH "GIT\-COMMIT\-TREE" "1" "01/19/2007" "" ""
+.TH "GIT\-COMMIT\-TREE" "1" "02/19/2007" "" ""
 .\" disable hyphenation
 .nh
 .\" disable justification (adjust text to left margin only)
@@ -84,22 +84,22 @@ The commit log messages are uninterpreted sequence of non\-NUL bytes.
 Although we encourage that the commit log messages are encoded in UTF\-8, both the core and git Porcelain are designed not to force UTF\-8 on projects. If all participants of a particular project find it more convenient to use legacy encodings, git does not forbid it. However, there are a few things to keep in mind.
 .TP 3
 1.
-git\-commit\-tree (hence, git\-commit which uses it) issues 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:
+git\-commit\-tree (hence, git\-commit which uses it) issues 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 i18n.commitencoding in .git/config file, like this:
 .sp
 .nf
-[core]
+[i18n]
         commitencoding = ISO\-8859\-1
 .fi
-Commit objects created with the above setting record the value of core.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.
+Commit objects created with the above setting record the value 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.
 .TP
 2.
-git\-log, git\-show and friends looks at the encoding 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:
+git\-log, git\-show and friends looks at the encoding 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 i18n.logoutputencoding in .git/config file, like this:
 .sp
 .nf
-[core]
+[i18n]
         logoutputencoding = ISO\-8859\-1
 .fi
-If you do not have this configuration variable, the value of core.commitencoding is used instead.
+If you do not have this configuration variable, the value of 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 object level, because re\-coding to UTF\-8 is not necessarily a reversible operation.
 .SH "SEE ALSO"

diff --git a/man1/git-commit.1 b/man1/git-commit.1
index ef890c5f758ddc9734612c313d70d03bad6f181d..d2b4c4105c9c0b43c347791915152ff04c20e19a 100644 (file)
--- a/man1/git-commit.1
+++ b/man1/git-commit.1
@@ -2,7 +2,7 @@
 .\" It was generated using the DocBook XSL Stylesheets (version 1.69.1).
 .\" Instead of manually editing it, you probably should edit the DocBook XML
 .\" source for it and then use the DocBook XSL Stylesheets to regenerate it.
-.TH "GIT\-COMMIT" "1" "01/25/2007" "" ""
+.TH "GIT\-COMMIT" "1" "02/19/2007" "" ""
 .\" disable hyphenation
 .nh
 .\" disable justification (adjust text to left margin only)
@@ -147,22 +147,22 @@ The commit log messages are uninterpreted sequence of non\-NUL bytes.
 Although we encourage that the commit log messages are encoded in UTF\-8, both the core and git Porcelain are designed not to force UTF\-8 on projects. If all participants of a particular project find it more convenient to use legacy encodings, git does not forbid it. However, there are a few things to keep in mind.
 .TP 3
 1.
-git\-commit\-tree (hence, git\-commit which uses it) issues 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:
+git\-commit\-tree (hence, git\-commit which uses it) issues 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 i18n.commitencoding in .git/config file, like this:
 .sp
 .nf
-[core]
+[i18n]
         commitencoding = ISO\-8859\-1
 .fi
-Commit objects created with the above setting record the value of core.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.
+Commit objects created with the above setting record the value 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.
 .TP
 2.
-git\-log, git\-show and friends looks at the encoding 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:
+git\-log, git\-show and friends looks at the encoding 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 i18n.logoutputencoding in .git/config file, like this:
 .sp
 .nf
-[core]
+[i18n]
         logoutputencoding = ISO\-8859\-1
 .fi
-If you do not have this configuration variable, the value of core.commitencoding is used instead.
+If you do not have this configuration variable, the value of 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 object level, because re\-coding to UTF\-8 is not necessarily a reversible operation.
 .SH "ENVIRONMENT VARIABLES"

diff --git a/man1/git-log.1 b/man1/git-log.1
index e6b4b1379dcee91e8b89a3d9ccb906930900affd..3b9738ae6e87e43c4fb5f643143a758b1a31b961 100644 (file)
--- a/man1/git-log.1
+++ b/man1/git-log.1
@@ -2,7 +2,7 @@
 .\" It was generated using the DocBook XSL Stylesheets (version 1.69.1).
 .\" Instead of manually editing it, you probably should edit the DocBook XML
 .\" source for it and then use the DocBook XSL Stylesheets to regenerate it.
-.TH "GIT\-LOG" "1" "02/09/2007" "" ""
+.TH "GIT\-LOG" "1" "02/19/2007" "" ""
 .\" disable hyphenation
 .nh
 .\" disable justification (adjust text to left margin only)
@@ -158,22 +158,22 @@ The commit log messages are uninterpreted sequence of non\-NUL bytes.
 Although we encourage that the commit log messages are encoded in UTF\-8, both the core and git Porcelain are designed not to force UTF\-8 on projects. If all participants of a particular project find it more convenient to use legacy encodings, git does not forbid it. However, there are a few things to keep in mind.
 .TP 3
 1.
-git\-commit\-tree (hence, git\-commit which uses it) issues 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:
+git\-commit\-tree (hence, git\-commit which uses it) issues 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 i18n.commitencoding in .git/config file, like this:
 .sp
 .nf
-[core]
+[i18n]
         commitencoding = ISO\-8859\-1
 .fi
-Commit objects created with the above setting record the value of core.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.
+Commit objects created with the above setting record the value 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.
 .TP
 2.
-git\-log, git\-show and friends looks at the encoding 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:
+git\-log, git\-show and friends looks at the encoding 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 i18n.logoutputencoding in .git/config file, like this:
 .sp
 .nf
-[core]
+[i18n]
         logoutputencoding = ISO\-8859\-1
 .fi
-If you do not have this configuration variable, the value of core.commitencoding is used instead.
+If you do not have this configuration variable, the value of 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 object level, because re\-coding to UTF\-8 is not necessarily a reversible operation.
 .SH "AUTHOR"

diff --git a/man1/git-show.1 b/man1/git-show.1
index 029fbe1ff52e34ba6ffbcd7cee8b3b4da16cda63..ab3f4e73ddcd63a889f624d8520041149b83be48 100644 (file)
--- a/man1/git-show.1
+++ b/man1/git-show.1
@@ -2,7 +2,7 @@
 .\" It was generated using the DocBook XSL Stylesheets (version 1.69.1).
 .\" Instead of manually editing it, you probably should edit the DocBook XML
 .\" source for it and then use the DocBook XSL Stylesheets to regenerate it.
-.TH "GIT\-SHOW" "1" "02/09/2007" "" ""
+.TH "GIT\-SHOW" "1" "02/19/2007" "" ""
 .\" disable hyphenation
 .nh
 .\" disable justification (adjust text to left margin only)
@@ -155,22 +155,22 @@ The commit log messages are uninterpreted sequence of non\-NUL bytes.
 Although we encourage that the commit log messages are encoded in UTF\-8, both the core and git Porcelain are designed not to force UTF\-8 on projects. If all participants of a particular project find it more convenient to use legacy encodings, git does not forbid it. However, there are a few things to keep in mind.
 .TP 3
 1.
-git\-commit\-tree (hence, git\-commit which uses it) issues 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:
+git\-commit\-tree (hence, git\-commit which uses it) issues 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 i18n.commitencoding in .git/config file, like this:
 .sp
 .nf
-[core]
+[i18n]
         commitencoding = ISO\-8859\-1
 .fi
-Commit objects created with the above setting record the value of core.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.
+Commit objects created with the above setting record the value 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.
 .TP
 2.
-git\-log, git\-show and friends looks at the encoding 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:
+git\-log, git\-show and friends looks at the encoding 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 i18n.logoutputencoding in .git/config file, like this:
 .sp
 .nf
-[core]
+[i18n]
         logoutputencoding = ISO\-8859\-1
 .fi
-If you do not have this configuration variable, the value of core.commitencoding is used instead.
+If you do not have this configuration variable, the value of 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 object level, because re\-coding to UTF\-8 is not necessarily a reversible operation.
 .SH "AUTHOR"