From: Jay Soffian <jaysoffian@gmail.com>
To: Constantine Plotnikov <constantine.plotnikov@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Q: description of file name encoding approach used by git
Date: Wed, 11 Feb 2009 11:08:48 -0500 [thread overview]
Message-ID: <76718490902110808g47b3ce0bm24419c89b5cb4aaa@mail.gmail.com> (raw)
In-Reply-To: <85647ef50902110356l19870259t9de22fd8827ac144@mail.gmail.com>
On Wed, Feb 11, 2009 at 6:56 AM, Constantine Plotnikov
<constantine.plotnikov@gmail.com> wrote:
> 3. As I understand, there is an unresolved problem with Mac OSX HFS+
> case insensitive file system due to file name normalization.
HFS+ can be configured to be case-sensitive, though it is not by
default. However, this is only a problem if the repo contains > 1
filenames that collide in a case-insensitive filesystem, since HFS+ is
case-preserving.
The larger HFS+ problem is that it performs Unicode NFD normalization,
which is unfortunately lossy. There are some good links about the
topic here: https://bugs.launchpad.net/bzr/+bug/172383
j.
prev parent reply other threads:[~2009-02-11 16:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-11 11:56 Q: description of file name encoding approach used by git Constantine Plotnikov
2009-02-11 16:08 ` Jay Soffian [this message]
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=76718490902110808g47b3ce0bm24419c89b5cb4aaa@mail.gmail.com \
--to=jaysoffian@gmail.com \
--cc=constantine.plotnikov@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).