All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: Brian Gernhardt <benji@silverinsanity.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Distinguish branches by more than case in tests.
Date: Fri, 06 Apr 2007 14:47:38 -0700	[thread overview]
Message-ID: <7v7ispjhtx.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20070406054204.GA13108@Hermes.local> (Brian Gernhardt's message of "Fri, 6 Apr 2007 01:42:04 -0400")

Brian Gernhardt <benji@silverinsanity.com> 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.

  reply	other threads:[~2007-04-06 21:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-06  5:42 [PATCH] Distinguish branches by more than case in tests Brian Gernhardt
2007-04-06 21:47 ` Junio C Hamano [this message]
2007-04-06 22:06   ` Linus Torvalds
2007-04-06 23:02     ` Randal L. Schwartz
2007-04-06 23:22       ` Bill Lear
2007-04-06 23:41       ` Linus Torvalds
2007-04-06 23:52         ` Bill Lear
2007-04-07  0:18         ` Kyle McMartin

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

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

  git send-email \
    --in-reply-to=7v7ispjhtx.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=benji@silverinsanity.com \
    --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. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.