[PATCH 1/3] i18n.txt: camel case and monospace "i18n.commitEncoding"
- From
Denton Liu <liu.denton@gmail.com>
- Date
- Feb 23, 2021, 06:39 UTC
- Message-ID
- <cc48b125166a241ef5f24138fd161223ab35e361.1614062288.git.liu.denton@gmail.com>
- In-Reply-To
- <cover.1614062288.git.liu.denton@gmail.com>
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> --- Documentation/i18n.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/i18n.txt b/Documentation/i18n.txt index 7e36e5b55b..6c6baeeeb7 100644 --- a/Documentation/i18n.txt +++ b/Documentation/i18n.txt @@ -38,7 +38,7 @@ mind. 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 - have i18n.commitencoding in `.git/config` file, like this: + have `i18n.commitEncoding` in `.git/config` file, like this: + ------------ [i18n]
-- 2.30.0.478.g8a0d178c01