From: Alex Riesen <raa.lkml@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jul 2009, #01; Mon, 06)
Date: Tue, 7 Jul 2009 21:57:14 +0200 [thread overview]
Message-ID: <81b0412b0907071257q14bb544dp99846f2a35fbada2@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.01.0907071142330.3210@localhost.localdomain>
On Tue, Jul 7, 2009 at 21:17, Linus
Torvalds<torvalds@linux-foundation.org> wrote:
> So right now, my personal opinion is:
>
> - let's just face the fact that the only sane filename representation is
> NFC UTF-8. Show filenames as UTF-8 when possible, rather than quoting
> them.
>
> - Do case (b) above: add support for converting NFD -> NFC at readdir()
> time, so that OS X people can use UTF-8 sanely.
>
> - add a "binary encoding" mode to filesystems that actually use Latin1,
> just so that if people use Latin1 or Shift-JIS filesystem encodings, we
> promise that we'll never munge those kinds of names.
>
> - Maybe we'd make the "binary encoding" (which is effectively existing
> git behavior) be the default on non-OSX platforms.
>
> but that's just my gut feel from trying to weigh the costs of trying to do
> something more involved against the costs of OS X support and just letting
> crazy encodings exist in their own little worlds. So a development group
> that uses Shift-JIS (or Latin1) would be able to work internally with git
> that way, but would not be able to sanely work with the world at large
> that uses UTF-8.
Maybe we could at least let the user save the encoding of file names
in the tree objects somehow?
next prev parent reply other threads:[~2009-07-07 19:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-06 18:32 What's cooking in git.git (Jul 2009, #01; Mon, 06) Junio C Hamano
2009-07-06 20:29 ` Marcus Camen
2009-07-06 21:38 ` Junio C Hamano
2009-07-06 22:03 ` Marcus Camen
2009-07-06 22:34 ` Junio C Hamano
2009-07-06 23:42 ` Jakub Narebski
2009-07-07 2:18 ` Mark Lodato
2009-07-07 21:11 ` Jeff King
2009-07-07 6:30 ` Johannes Sixt
2009-07-07 19:17 ` Linus Torvalds
2009-07-07 19:57 ` Alex Riesen [this message]
2009-07-07 22:13 ` Linus Torvalds
2009-07-07 20:08 ` Johannes Schindelin
2009-07-07 20:13 ` Shawn O. Pearce
2009-07-07 22:19 ` Junio C Hamano
2009-07-07 22:28 ` Shawn O. Pearce
2009-07-08 13:42 ` notes, was " Johannes Schindelin
2009-07-08 5:39 ` Stephen Boyd
2009-07-08 6:38 ` Johannes Sixt
2009-07-10 5:05 ` Christian Couder
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=81b0412b0907071257q14bb544dp99846f2a35fbada2@mail.gmail.com \
--to=raa.lkml@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=torvalds@linux-foundation.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).