From: Paul Betts <paul@paulbetts.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: Path character encodings
Date: Mon, 5 Mar 2012 14:02:32 -0800 [thread overview]
Message-ID: <20120305220232.GA18247@jupiter.local> (raw)
In-Reply-To: <7vipiizpyn.fsf@alter.siamese.dyndns.org>
Hi Junio,
On Mon, Mar 05, 2012 at 01:40:32PM -0800, Junio C Hamano wrote:
> Hmph, I do not see a reason to make a huge molehill in this. The
> pathnames are of unspecified encoding, and if a project declares
> that they always use UTF-8, that would be great.
I would like to propose, that Git codifies-as-required the majority case
today, that trees should *only* be encoded in UTF-8 going forward.
> Why does git itself have to do anything about it, and how would it help
> users without hurting other git users who are not involved in such a
> project?
My concern is that users will not know what's happening or how to fix it,
they'll just see messed up paths and assume Git is broken. Even a warning
message would give users something explicit to put into Google to find a
solution for. Not many people will possess the Git-Fu required to manage
filter-branch.
--
Paul Betts <paul@paulbetts.org>
next prev parent reply other threads:[~2012-03-05 22:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-05 21:26 Path character encodings Paul Betts
2012-03-05 21:40 ` Junio C Hamano
2012-03-05 22:02 ` Paul Betts [this message]
2012-03-05 22:18 ` Junio C Hamano
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=20120305220232.GA18247@jupiter.local \
--to=paul@paulbetts.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).