git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git format-patch displays weird chars when filename includes non-ascii chars

From
Junio C Hamano <gitster@pobox.com>
Date
May 14, 2024, 21:38 UTC
Message-ID
<xmqq1q643whe.fsf@gitster.g>
In-Reply-To
<ZkPNHqAUemfdfaFD@tapette.crustytoothpaste.net>
"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
Previous: brian m. carlsonNext: Yongmin
Message 3 of 4 in “git format-patch displays weird chars when filename includes non-ascii chars”
  1. YongminMay 14, 2024
  2. brian m. carlsonMay 14, 2024
  3. Junio C HamanoMay 14, 2024
  4. YongminMay 15, 2024

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.