From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: Non-ASCII paths and git-cvsserver
Date: Mon, 13 Nov 2006 15:20:44 +0100 [thread overview]
Message-ID: <ej9utk$44p$1@sea.gmane.org> (raw)
In-Reply-To: 45587A09.3020605@b-i-t.de
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.
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2006-11-13 14:19 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 [this message]
2006-11-13 18:30 ` Robin Rosenberg
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='ej9utk$44p$1@sea.gmane.org' \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
/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).