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

Re: [PATCH] gitk: use UTF-8 encoding

From
HAH. Peter Anvin <hpa@zytor.com>
Date
Oct 6, 2005, 05:00 UTC
Message-ID
<4344AF8A.1040504@zytor.com>
In-Reply-To
<7vvf0b9t0d.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
Show 9 quoted lines
> Pavel Roskin <proski@gnu.org> writes:
> 
>>gitk should try to use UTF-8 encoding for system operations, such as
>>reading and writing files and git output.
> 
> I agree about commit messages, but I am not so sure about the
> file contents (aka user data).  Is it possible to control them
> separately?
>

git needs to be able to treat user data as arbitrary binary blobs. However, if interpreting as text, UTF-8 is the right default, at least.

	-hpa
Previous: Junio C HamanoNext: Pavel Roskin
Message 3 of 4 in “gitk: use UTF-8 encoding”
  1. gitk: use UTF-8 encodingPavel Roskin, Oct 6, 2005
  2. Junio C HamanoOct 6, 2005
  3. H. Peter AnvinOct 6, 2005
  4. Pavel RoskinOct 6, 2005

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.