diff options
author | Junio C Hamano <junio@hera.kernel.org> | 2008-07-06 05:20:31 +0000 |
---|---|---|
committer | Junio C Hamano <junio@hera.kernel.org> | 2008-07-06 05:20:31 +0000 |
commit | ba4b9286c25f18c7ebbb809ee5732a7810377ab6 (patch) | |
tree | 390507328a7564b65dc803683c34235700b97409 /i18n.txt | |
parent | 05bf9c54a827e48b2b576488f5170a3490b5180e (diff) | |
download | git-htmldocs-ba4b9286c25f18c7ebbb809ee5732a7810377ab6.tar.gz |
Autogenerated HTML docs for v1.5.6.2-212-g08b5
Diffstat (limited to 'i18n.txt')
-rw-r--r-- | i18n.txt | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -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-tree' (hence, 'git-commit' which uses it) 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 @@ -37,7 +37,7 @@ 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. -. `git-log`, `git-show` and friends looks at the `encoding` +. '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 |