File tree Expand file tree Collapse file tree 2 files changed +11
-10
lines changed
Expand file tree Collapse file tree 2 files changed +11
-10
lines changed Original file line number Diff line number Diff line change @@ -196,11 +196,12 @@ whitespace::
196196verbatim::
197197 Do not change the message at all.
198198scissors::
199- Same as `whitespace`, except that everything from (and
200- including) the line
201- "`# ------------------------ >8 ------------------------`"
202- is truncated if the message is to be edited. "`#`" can be
203- customized with core.commentChar.
199+ Same as `whitespace` except that everything from (and including)
200+ the line found below is truncated, if the message is to be edited.
201+ "`#`" can be customized with core.commentChar.
202+
203+ # ------------------------ >8 ------------------------
204+
204205default::
205206 Same as `strip` if the message is to be edited.
206207 Otherwise `whitespace`.
Original file line number Diff line number Diff line change @@ -42,27 +42,27 @@ mind.
4242+
4343------------
4444[i18n]
45- commitencoding = ISO-8859-1
45+ commitEncoding = ISO-8859-1
4646------------
4747+
4848Commit objects created with the above setting record the value
49- of `i18n.commitencoding ` in its `encoding` header. This is to
49+ of `i18n.commitEncoding ` in its `encoding` header. This is to
5050help other people who look at them later. Lack of this header
5151implies that the commit log message is encoded in UTF-8.
5252
5353. 'git log', 'git show', 'git blame' and friends look at the
5454 `encoding` header of a commit object, and try to re-code the
5555 log message into UTF-8 unless otherwise specified. You can
5656 specify the desired output encoding with
57- `i18n.logoutputencoding ` in `.git/config` file, like this:
57+ `i18n.logOutputEncoding ` in `.git/config` file, like this:
5858+
5959------------
6060[i18n]
61- logoutputencoding = ISO-8859-1
61+ logOutputEncoding = ISO-8859-1
6262------------
6363+
6464If you do not have this configuration variable, the value of
65- `i18n.commitencoding ` is used instead.
65+ `i18n.commitEncoding ` is used instead.
6666
6767Note that we deliberately chose not to re-code the commit log
6868message when a commit is made to force UTF-8 at the commit
You can’t perform that action at this time.
0 commit comments