From: Junio C Hamano <gitster@pobox.com>
To: "brian m. carlson" <sandals@crustytoothpaste.net>
Cc: Yongmin <revi@omglol.email>, git@vger.kernel.org
Subject: Re: git format-patch displays weird chars when filename includes non-ascii chars
Date: Tue, 14 May 2024 14:38:21 -0700 [thread overview]
Message-ID: <xmqq1q643whe.fsf@gitster.g> (raw)
In-Reply-To: <ZkPNHqAUemfdfaFD@tapette.crustytoothpaste.net> (brian m. carlson's message of "Tue, 14 May 2024 20:44:14 +0000")
"brian m. carlson" <sandals@crustytoothpaste.net> writes:
> Thus, Git prefers to encode names in a way that is unambiguous and
> doesn't lead to mangling. It is inconvenient that legitimate UTF-8 file
> names don't get rendered properly, though. I don't _believe_ there's an
> option to show the regular UTF-8, but I could be wrong.
$ git config --global core.quotepath false
next prev parent reply other threads:[~2024-05-14 21:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-14 15:31 git format-patch displays weird chars when filename includes non-ascii chars Yongmin
2024-05-14 20:44 ` brian m. carlson
2024-05-14 21:38 ` Junio C Hamano [this message]
2024-05-15 5:40 ` Yongmin
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqq1q643whe.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=revi@omglol.email \
--cc=sandals@crustytoothpaste.net \
/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.
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 NNTP newsgroup(s).