From: Stephen Bash <bash@genarts.com>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: git@vger.kernel.org, Dan Loewenherz <dloewenherz@gmail.com>
Subject: Re: Does changing filename case breaks git's rename heuristic?
Date: Fri, 27 Aug 2010 12:22:54 -0400 (EDT) [thread overview]
Message-ID: <29718856.121438.1282926174106.JavaMail.root@mail.hq.genarts.com> (raw)
In-Reply-To: <4C77DDDC.8070407@drmicha.warpmail.net>
> > I'm using a Mac with a journaled filesystem and Git version 1.7.2.1.
>
> The journalling is no problem, but HFS is. I'm no Macxpert but if I
> remember correctly, then under HFS "readme" and "README" are the same
> file, i.e. HFS only remembers how you want it spelled. People will
> correct me where I'm wrong.
>
> Your test script should produce the expected result if you use, say,
> "readme" and "RAEDME" , i.e. names which differ by more than just
> case.
It's a problem on some (most?) Macs. A while back Apple introduced an option to format a partition as case sensitive (Wikipedia implies 10.3 introduced this feature). For a long time after the feature was introduced the factory install continued to be not case sensitive, but I don't know if that's still the case (no pun intended).
Stephen
next prev parent reply other threads:[~2010-08-27 16:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-27 4:57 Does changing filename case breaks git's rename heuristic? Dan Loewenherz
2010-08-27 5:36 ` Ramkumar Ramachandra
2010-08-27 8:00 ` Michael J Gruber
2010-08-27 14:52 ` Dan Loewenherz
2010-08-27 15:46 ` Michael J Gruber
2010-08-27 16:22 ` Stephen Bash [this message]
2010-08-27 20:02 ` Jay Soffian
2010-08-28 10:39 ` Ævar Arnfjörð Bjarmason
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=29718856.121438.1282926174106.JavaMail.root@mail.hq.genarts.com \
--to=bash@genarts.com \
--cc=dloewenherz@gmail.com \
--cc=git@drmicha.warpmail.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).