summaryrefslogtreecommitdiffstats
path: root/i18n.txt
diff options
context:
space:
mode:
authorJunio C Hamano <junio@hera.kernel.org>2008-09-04 00:24:07 +0000
committerJunio C Hamano <junio@hera.kernel.org>2008-09-04 00:24:07 +0000
commit3727619bbead20ee102505c799e1b0737f0c04f7 (patch)
tree36e3a346691e77bc0d8ff2123e571143e0b22e8a /i18n.txt
parenta2f4662f592080968a8ce848d3e5d84003a6c20d (diff)
downloadgit-htmldocs-3727619bbead20ee102505c799e1b0737f0c04f7.tar.gz
Autogenerated HTML docs for v1.6.0.1-216-g1b23a
Diffstat (limited to 'i18n.txt')
-rw-r--r--i18n.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/i18n.txt b/i18n.txt
index fb0d7da56..d2970f835 100644
--- a/i18n.txt
+++ b/i18n.txt
@@ -21,7 +21,7 @@ project find it more convenient to use legacy encodings, git
does not forbid it. However, there are a few things to keep in
mind.
-. 'git-commit-tree' (hence, 'git-commit' which uses it) issues
+. 'git-commit' and 'git-commit-tree' issues
a 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