i18n.txt: camel case and monospace "i18n.commitEncoding"
In 95791be750 (doc: camelCase the i18n config variables to improve readability, 2017-07-17), the other i18n config variables were camel cased. However, this one instance was missed. Camel case and monospace "i18n.commitEncoding" so that it matches the surrounding text. Signed-off-by: Denton Liu <liu.denton@gmail.com> [jc: fixed 3 other mistakes that are exactly the same] Signed-off-by: Junio C Hamano <gitster@pobox.com>
Denton Liu committed
Feb 24, 2021 at 12:26 UTC
77645b5daa6eaa4ab0502ef00817c87f7666bfec
3 files changed
+4
-4
Documentation/git-am.txt
+1
-1
@@ -79,7 +79,7 @@ OPTIONS
79
Pass `-u` flag to 'git mailinfo' (see linkgit:git-mailinfo[1]).
80
The proposed commit log message taken from the e-mail
81
is re-coded into UTF-8 encoding (configuration variable
82
- `i18n.commitencoding` can be used to specify project's
82
+ `i18n.commitEncoding` can be used to specify project's
83
preferred encoding if it is not UTF-8).
84
+
85
This was optional in prior versions of git, but now it is the
Documentation/git-mailinfo.txt
+2
-2
@@ -53,7 +53,7 @@ character.
53
The commit log message, author name and author email are
54
taken from the e-mail, and after minimally decoding MIME
55
transfer encoding, re-coded in the charset specified by
56
- i18n.commitencoding (defaulting to UTF-8) by transliterating
56
+ `i18n.commitEncoding` (defaulting to UTF-8) by transliterating
57
them. This used to be optional but now it is the default.
58
+
59
Note that the patch is always used as-is without charset
@@ -61,7 +61,7 @@ conversion, even with this flag.
61
62
--encoding=<encoding>::
63
Similar to -u. But when re-coding, the charset specified here is
64
- used instead of the one specified by i18n.commitencoding or UTF-8.
64
+ used instead of the one specified by `i18n.commitEncoding` or UTF-8.
65
66
-n::
67
Disable all charset re-coding of the metadata.
Documentation/i18n.txt
+1
-1
@@ -38,7 +38,7 @@ mind.
38
a warning if the commit log message given to it does not look
39
like a valid UTF-8 string, unless you explicitly say your
40
project uses a legacy encoding. The way to say this is to
41
- have i18n.commitencoding in `.git/config` file, like this:
41
+ have `i18n.commitEncoding` in `.git/config` file, like this:
42
+
43
------------
44
[i18n]