summaryrefslogtreecommitdiff
path: root/t/annotate-tests.sh
diff options
context:
space:
mode:
authorLibravatar Jeff King <peff@peff.net>2021-08-27 14:32:06 -0400
committerLibravatar Junio C Hamano <gitster@pobox.com>2021-08-27 12:45:45 -0700
commit1e93770888d3e71422f9f8defab216f1ebf977c3 (patch)
treefd0ec27964f6e8a61889d43fdb66a187f2d65d39 /t/annotate-tests.sh
parentlogmsg_reencode(): warn when iconv() fails (diff)
downloadtgif-1e93770888d3e71422f9f8defab216f1ebf977c3.tar.xz
docs: use "character encoding" to refer to commit-object encoding
The word "encoding" can mean a lot of things (e.g., base64 or quoted-printable encoding in emails, HTML entities, URL encoding, and so on). The documentation for i18n.commitEncoding and i18n.logOutputEncoding uses the phrase "character encoding" to make this more clear. Let's use that phrase in other places to make it clear what kind of encoding we are talking about. This patch covers the gui.encoding option, as well as the --encoding option for git-log, etc (in this latter case, I word-smithed the sentence a little at the same time). That, coupled with the mention of iconv in the --encoding description, should make this more clear. The other spot I looked at is the working-tree-encoding section of gitattributes(5). But it gives specific examples of encodings that I think make the meaning pretty clear already. Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/annotate-tests.sh')
0 files changed, 0 insertions, 0 deletions