git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Kevin Ballard <kevin@sb.org>
To: git@vger.kernel.org
Subject: Re: Re-casing directories on case-insensitive systems
Date: Fri, 11 Jan 2008 20:16:40 -0500	[thread overview]
Message-ID: <B2968E86-D43E-4F5E-921F-DF8A15886C98@sb.org> (raw)
In-Reply-To: <alpine.LSU.1.00.0801120139170.8333@wbgn129.biozentrum.uni-wuerzburg.de>

[-- Attachment #1: Type: text/plain, Size: 1600 bytes --]

On Jan 11, 2008, at 7:40 PM, Johannes Schindelin wrote:

> On Fri, 11 Jan 2008, Junio C Hamano wrote:
>
>> Kevin Ballard <kevin@sb.org> writes:
>>
>>> Is there a reason for this? It seems like it would be trivial to end
>>> up with misdiagnosed "untracked" files when using any language other
>>> than English given this behaviuor.
>>
>> No.  The assumption of the code has always been that sane filesystems
>> would return from readdir() the names you gave from creat().
>
> We do not really have to rehash that whole discussion for the Nth  
> time, do
> we?


Apparently so. By Junio's definition, HFS+ is not a sane filesystem,  
and as git grows more popular with OS X users, this issue is going to  
crop up more frequently.

According to the HFS+ Volume Format technote[1], filenames in HFS+ are  
stored in normalized, canonical order. To be more specific, they're  
stored in a special apple variant of Unicode Normal Form D (the  
special variant is for preserving round-trip with older encodings with  
certain codepoint ranges[2]).

In other words, if you hand an HFS+ filesystem a filename that  
contains unicode characters, what you get back later may be in a  
different format. And that's going to be a problem if git doesn't deal  
with this.

[1]: http://developer.apple.com/technotes/tn/tn1150.html#UnicodeSubtleties
[2]: http://developer.apple.com/qa/qa2001/qa1173.html

Note: CC list stripped because this is a re-sent email, as the list  
bounced the last one that contained a text/html alternate.

-- 
Kevin Ballard
http://kevin.sb.org
kevin@sb.org
http://www.tildesoft.com



[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 2432 bytes --]

  reply	other threads:[~2008-01-12  1:17 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-11 20:19 Re-casing directories on case-insensitive systems Kevin Ballard
2008-01-11 21:09 ` Kevin Ballard
2008-01-11 21:19   ` Kevin Ballard
2008-01-11 21:25   ` Linus Torvalds
2008-01-11 21:59   ` Robin Rosenberg
2008-01-11 21:18 ` Linus Torvalds
2008-01-11 21:29 ` Johannes Schindelin
2008-01-11 21:44   ` Kevin Ballard
2008-01-11 22:05     ` Johannes Schindelin
2008-01-11 22:08     ` Linus Torvalds
2008-01-11 23:10       ` David Kastrup
2008-01-11 23:12         ` Kevin Ballard
2008-01-11 23:26       ` Robin Rosenberg
2008-01-12  0:03         ` Kevin Ballard
2008-01-12  0:15           ` Robin Rosenberg
2008-01-12  0:25             ` Kevin Ballard
2008-01-12  0:27               ` Junio C Hamano
2008-01-12  0:40                 ` Johannes Schindelin
2008-01-12  1:16                   ` Kevin Ballard [this message]
2008-01-12  1:30                     ` Junio C Hamano
2008-01-12  1:43                       ` Kevin Ballard
2008-01-12 12:07                         ` David Kastrup
2008-01-12 15:03                         ` Dmitry Potapov
2008-01-12  0:37         ` Junio C Hamano
2008-01-12  0:57           ` Robin Rosenberg
2008-01-12 16:33             ` Johannes Schindelin
2008-01-12 14:46       ` Dmitry Potapov
2008-01-12 18:47         ` Linus Torvalds
2008-01-12 19:29           ` Dmitry Potapov

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=B2968E86-D43E-4F5E-921F-DF8A15886C98@sb.org \
    --to=kevin@sb.org \
    --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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).