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

Linus Torvalds [off-list ref] writes:

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?

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.

The thing is, even if you mange to educate them all, that broken
filesystem, and other filesystems with similar brokenness, do
not go away.  If your ultimate objective is to declare that it
is the right thing for git not to support such broken
filesystems, and to make everybody agree to it, that is fine.
Please keep pouring fuel to the fire.  But if that is not the
case, we would need to devise a way to help lives easier for the
unfortunate people who are stuck on such filesystems.  They may
not even realize that they are unfortunate now, and I agree that
some education is justified, but this thread has raged on long
enough to salvage any salvageable lost souls (the remaining ones
may be beyond salvation but let's not waste time on them).

I'd rather see our mental bandwidth spent on coming up with a
workable workaround for such broken filesystems, while not
hurting use of git on sane platforms.

I fear it might have to end up to be very messy and slow,
though.

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"