From: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
To: Jeff King <peff@peff.net>
Cc: "Carlos Martín Nieto" <cmn@elego.de>,
"Chris Patti" <cpatti@gmail.com>,
git@vger.kernel.org
Subject: Re: Odd issue - The Diffs That WILL NOT DIE.
Date: Wed, 05 Sep 2012 21:38:17 +0200 [thread overview]
Message-ID: <5047AA29.2000003@dewire.com> (raw)
In-Reply-To: <20111207230625.GC21852@sigill.intra.peff.net>
Jeff King skrev 2011-12-08 00.06:
> On Wed, Dec 07, 2011 at 11:58:27PM +0100, Carlos Martín Nieto wrote:
>
>> If you want to use OSX to develop this project, you'll have to either
>> rename one of those files or set your filesystem to be case-sensitive
>> (and unset core.ignorecase afterwards). From what I've heard, the OS
>> itself will work fine with a case-sensitive filesystem, but not all
>> applications might. YMMV.
>
> I've never done it, but my understanding is that for HFS+, going
> case-sensitive is not a simple flip of a switch, but you have to
> actually make a new filesystem. Given that complexity, and the fact that
> some other apps might not like it, your best bet might be to create a
> new case-sensitive filesystem in a loopback file, and then mount that
> just for this project.
>
> I'm not sure of the exact commands under OS X, but I'm sure some
> googling could probably turn up a solution.
The disk tool does this for you. Can't be much easier than it is.
-- robin
next prev parent reply other threads:[~2012-09-05 19:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-06 21:43 Odd issue - The Diffs That WILL NOT DIE Chris Patti
2011-12-06 21:47 ` Frans Klaver
2011-12-06 21:51 ` Carlos Martín Nieto
2011-12-07 16:54 ` Chris Patti
2011-12-07 17:20 ` Philippe Vaucher
2011-12-07 18:05 ` Chris Patti
2011-12-07 18:16 ` Chris Patti
2011-12-07 22:03 ` Jeff King
2011-12-07 22:24 ` Chris Patti
2011-12-07 22:30 ` Chris Patti
2011-12-07 22:58 ` Carlos Martín Nieto
2011-12-07 23:06 ` Jeff King
2012-09-05 19:38 ` Robin Rosenberg [this message]
2011-12-07 23:03 ` Jeff King
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=5047AA29.2000003@dewire.com \
--to=robin.rosenberg.lists@dewire.com \
--cc=cmn@elego.de \
--cc=cpatti@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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.