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

Re: Non-ASCII paths and git-cvsserver

From
Robin Rosenberg <robin.rosenberg.lists@dewire.com>
Date
Nov 13, 2006, 18:30 UTC
Message-ID
<200611131930.18300.robin.rosenberg.lists@dewire.com>
In-Reply-To
<ej9utk$44p$1@sea.gmane.org>
måndag 13 november 2006 15:20 skrev Jakub Narebski:
Show 9 quoted lines
> sf wrote:
> > Thanks, Junio. Paths with umlauts are returned correctly now both in
> > UTF-8 and ISO-8859-1. I guess git-cvsserver is now as encoding agnostic
> > as git core.
>
> By the way, now that git has per user config file, ~/.gitconfig, perhaps
> it is time to add i18n.filesystemEncoding configuration variable, to
> automatically convert between filesystem encoding (somthing you usually
> don't have any control over) and UTF-8 encoding of paths in tree objects.

I'd prefer git to store filenames and comments in UTF-8 and convert on input/output when and if it is necessary rather than forcing everybody to take the hit. Most systems, but far from all, already use UTF-8 so it's a noop for them. The only reason I want conversion is for the years to come where we still live in two worlds of non-utf-8 and utf-8 and then forget about everything non-utf-8, rather than carry around the baggage forever.

Previous: Jakub NarebskiNext: Jakub Narebski
Message 6 of 11 in “Non-ASCII paths and git-cvsserver”
  1. sfNov 9, 2006
  2. Martin LanghoffNov 10, 2006
  3. Junio C HamanoNov 10, 2006
  4. sfNov 13, 2006
  5. Jakub NarebskiNov 13, 2006
  6. Robin RosenbergNov 13, 2006
  7. Jakub NarebskiNov 13, 2006
  8. Robin RosenbergNov 13, 2006
  9. Junio C HamanoNov 13, 2006
  10. Martin LanghoffNov 13, 2006
  11. sfNov 14, 2006

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.