Re: [PATCH] Use "-f" when adding files with odd names in t9200.

From: Brian Gernhardt <benji@silverinsanity.com>
Date: Feb 4, 2007, 16:35 UTC
Message-ID: <155A5E6A-9EC5-424B-A231-02EF1FE0FD2B@silverinsanity.com>
In-Reply-To: <7vlkje243u.fsf@assigned-by-dhcp.cox.net>

Shawn has already provided an example of what happens to a UTF8 string on OS X, so I won't provide a duplicate.

On Feb 3, 2007, at 6:50 PM, Junio C Hamano wrote:

Show 6 quoted lines

> I think it is fairly idiotic and obtuse for a filesystem to
> treat pathnames anything but a random sequence of bytes that is
> slash separated and NUL terminated.  I would need a really hard
> convincing to buy any path munging on the git side to match
> whatever a stupid filesystem does, especially because we do not
> live in the ideal Unicode/utf-8 only world.

That's what I was agreeing with. It drives me crazy that HFS+ is case-insensitive and now does bad things to UTF8 strings. And I didn't think that doing munging similar to the FS in git is a good idea for Git in general, but might be useful for a few people like myself to have. And it wouldn't break anything that isn't already broken.

Unfortunately my lack of understanding of ICU means I can't actually get the code to do anything useful, so it's a moot point.

~~ Brian