Re: git on MacOSX and files with decomposed utf-8 file names

Hi,

On Fri, 18 Jan 2008, Junio C Hamano wrote:

Linus Torvalds [off-list ref] writes:

quoted

On Fri, 18 Jan 2008, Peter Karlsson wrote:

quoted

But they are not different strings, they are canonically equivalent as
far as Unicode is concerned.

Fuck me with a spoon.

Why the hell cannot people see that "equivalent" and "same" are two 
totally different meanings.

Could people _please_ stop this already?

Welcome, voice of reason.

I think the sane people see the difference between equivalence
and sameness, and we established that a filesystem that mangles
the filenames behind user's back is a bad design.  Anybody who
followed the thread and still does not agree with you is, eh,
"ugly-and-stupid", as you might say ;-).  You cannot educate
them all.

Actually, I see some value in calling them names, see 
http://video.google.nl/videoplay?docid=-4216011961522818645 for why.

The thing is, even if you mange to educate them all, that broken 
filesystem, and other filesystems with similar brokenness, do not go 
away.

I was almost starting with hacking on this, but then the discussion 
annoyed me too much, and I asked myself for who I think I'd do this.

IMHO those people should ask "how could I begin to work on this".

Instead, they started a useless flamewar.

Now, back to the issue: Robin posted a link to his UTF-8 work.  While it 
is way too intrusive, and not limited to filenames at all, I think it has 
a few good pointers.

Ciao,
Dscho "who needs to calm down now"