From: "Christopher Yeleighton via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Christopher Yeleighton <giecrilj@stegny.2a.pl>,
Christopher Yeleighton <ne01026@shark.2a.pl>
Subject: [PATCH] pretty-options.txt: describe supported encoding
Date: Thu, 26 Aug 2021 21:34:28 +0000 [thread overview]
Message-ID: <pull.1079.git.git.1630013668862.gitgitgadget@gmail.com> (raw)
From: Christopher Yeleighton <ne01026@shark.2a.pl>
Please fix the manual for git log. It should say what encoding is recognised
(namely if supported by iconv(1), except that POSIX character maps of
iconv(1p) are not supported), and that an unrecognised encoding is ignored.
Signed-off-by: <ne01026@shark.2a.pl>
---
log: describe supported encoding
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-1079%2Fyecril71pl%2Fpatch-1-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-1079/yecril71pl/patch-1-v1
Pull-Request: https://github.com/git/git/pull/1079
Documentation/pretty-options.txt | 10 +++++++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/Documentation/pretty-options.txt b/Documentation/pretty-options.txt
index 27ddaf84a19..4f8376d681b 100644
--- a/Documentation/pretty-options.txt
+++ b/Documentation/pretty-options.txt
@@ -36,9 +36,13 @@ people using 80-column terminals.
The commit objects record the encoding used for the log message
in their encoding header; this option can be used to tell the
command to re-code the commit log message in the encoding
- preferred by the user. For non plumbing commands this
- defaults to UTF-8. Note that if an object claims to be encoded
- in `X` and we are outputting in `X`, we will output the object
+ preferred by the user.
+ The encoding must be a system encoding supported by iconv(1),
+ otherwise this option will be ignored.
+ POSIX character maps used by iconv(1p) are not supported.
+ For non-plumbing commands this defaults to UTF-8.
+ Note that if an object claims to be encoded in `X`
+ and we are outputting in `X`, we shall output the object
verbatim; this means that invalid sequences in the original
commit may be copied to the output.
base-commit: c4203212e360b25a1c69467b5a8437d45a373cac
--
gitgitgadget
next reply other threads:[~2021-08-26 21:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-26 21:34 Christopher Yeleighton via GitGitGadget [this message]
2021-08-27 10:46 ` [PATCH] pretty-options.txt: describe supported encoding Bagas Sanjaya
2021-08-27 11:47 ` Krzysztof Żelechowski
2021-08-27 11:51 ` [PATCH v2] " Krzysztof Żelechowski
2021-08-27 17:03 ` Junio C Hamano
2021-08-27 18:03 ` Jeff King
2021-08-27 23:20 ` Krzysztof Żelechowski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=pull.1079.git.git.1630013668862.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=giecrilj@stegny.2a.pl \
--cc=git@vger.kernel.org \
--cc=ne01026@shark.2a.pl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).