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

Re: GIT character codecs

From
Linus Torvalds <torvalds@osdl.org>
Date
Nov 13, 2005, 17:51 UTC
Message-ID
<Pine.LNX.4.64.0511130948020.3263@g5.osdl.org>
In-Reply-To
<20051113081443.38296.qmail@web26309.mail.ukl.yahoo.com>
On Sun, 13 Nov 2005, Marco Costalba wrote:
> 
> If encoding is a per-blob _and_ per-log message property a real solution, although cumbersone,
> could be that git stores encoding togheter with the blob and the commits.

We'd be much better off with just saying "we encourage people to use utf-8, but if you don't, just set your locale to make things show up properly".

utf-8 is clearly the future, and if we make git internally aware of locales, that's just going to complicate things. And usually for no good reason, since users don't really care that much.

I really hate codepages. I'd much rather say:
 - git is 8-bit clean, so you can use any damn encoding you want
 - utf-8 is strongly recommended for all the same reasons it's recommended 
   for anything else.
Hmm?
		Linus
Previous: Matthias Urlichs
Message 4 of 4 in “Re: GIT character codecs”
  1. Marco CostalbaNov 13, 2005
  2. Junio C HamanoNov 13, 2005
  3. Matthias UrlichsNov 14, 2005
  4. Linus TorvaldsNov 13, 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.