From: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Non-ASCII paths and git-cvsserver
Date: Mon, 13 Nov 2006 19:30:18 +0100 [thread overview]
Message-ID: <200611131930.18300.robin.rosenberg.lists@dewire.com> (raw)
In-Reply-To: <ej9utk$44p$1@sea.gmane.org>
måndag 13 november 2006 15:20 skrev Jakub Narebski:
> 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.
next prev parent reply other threads:[~2006-11-13 18:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-09 11:11 Non-ASCII paths and git-cvsserver sf
2006-11-10 18:59 ` Martin Langhoff
2006-11-10 19:49 ` Junio C Hamano
2006-11-13 13:58 ` sf
2006-11-13 14:20 ` Jakub Narebski
2006-11-13 18:30 ` Robin Rosenberg [this message]
2006-11-13 18:57 ` Jakub Narebski
2006-11-13 21:41 ` Robin Rosenberg
2006-11-13 19:48 ` Junio C Hamano
2006-11-13 18:22 ` Martin Langhoff
2006-11-14 10:40 ` sf
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=200611131930.18300.robin.rosenberg.lists@dewire.com \
--to=robin.rosenberg.lists@dewire.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
/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).