Re: [PATCH] Distinguish branches by more than case in tests.

Brian Gernhardt [off-list ref] writes:

The renaming without config test changed a branch from q to Q, which
fails on non-case sensitive file systems.  Change the test to use q
and q2.
---

Notably, HFS+ is not case sensitive.  IIRC there are others.  This isn't
a flaw of git, just a bad choice of branch names for certain systems.

Sigh.

I always wonder why people pay money to buy case insensitive
filesystems (MacOS is not free, is it?).

More mysterious is that there apparently are peole who are paid
to produce such systems (Apple has paid employees to work on
MacOS, doesn't it?).

The worst of all this is that I have to be careful not to break
things on such a system, and take a patch like this (admittedly,
you did the real fixing, so that is less work for me, but
still...).

And puzzlingly enough, I am not paid to do this ;-).

Thanks for the patch.  Will apply.

On Fri, 6 Apr 2007, Junio C Hamano wrote:

I always wonder why people pay money to buy case insensitive
filesystems (MacOS is not free, is it?).

More mysterious is that there apparently are peole who are paid
to produce such systems (Apple has paid employees to work on
MacOS, doesn't it?).

It's doubly strange, because:
 - it's basically impossible to do well
 - even *trying* to do it introduces other (even subtler) problems, like 
   locale-dependencies and trying to force some "canonical" encoding.

People who do it tend to universally do it because they haven't thought it 
through, and are supporting some older behaviour. And in the process they 
make their filesystem less reliable *and* slower.

		Linus