From: Wincent Colaiuta <win@wincent.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Andreas Ericsson <ae@op5.se>, Florian Weimer <fweimer@bfk.de>,
Reece Dunn <msclrhd@googlemail.com>,
git@vger.kernel.org
Subject: Re: git: cannot rename foo to Foo on a case-insensitive filesystem (e.g. on Windows)
Date: Wed, 29 Aug 2007 11:31:10 +0200 [thread overview]
Message-ID: <1BA15C6C-1F37-401B-B8D8-4BD147CF5225@wincent.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0708290321530.28586@racer.site>
El 29/8/2007, a las 4:23, Johannes Schindelin escribió:
> On Wed, 29 Aug 2007, Wincent Colaiuta wrote:
>
>> El 28/8/2007, a las 22:45, Johannes Schindelin escribi?:
>>
>>> On Tue, 28 Aug 2007, Wincent Colaiuta wrote:
>>>
>>>> Personally, I don't like HFS+ much at all, but your statement that
>>>> Mac OS X "doesn't even have a case sensitive filesystem" is false.
>>>
>>> It is right that they support it. But since the _default_ is case
>>> insensitive (but only as long as it is not _reporting_ file
>>> names), it
>>> is _as bad_ as "doesn't even have a case sensitive filesystem". No
>>> sophistry helps here.
>>
>> I don't think my correction qualifies as "sophistry" by any
>> reasonable
>> definition of the word. Andreas claimed that Apple had turned "a
>> perfectly decent unix-clone such as FreeBSD into some defect
>> monstrosity
>> that doesn't even have a case sensitive filesystem"; I merely
>> sought to
>> correct his misstatement.
>
> I acknowledged that.
>
> But it does not change the _meaning_ of Andreas' criticism. They
> took a
> perfectly sane system, and turned it into a mess.
I don't think it's productive to enter into arguments about whether a
particular operating system is a "monstrosity", "sane" or "a mess";
that's why I limited my comment to a correction of a factual
misstatement by Andreas and left the opinion part unchallenged. We
could have avoided this thread if instead of "doesn't even have a
case sensitive filesystem", he'd started his flame with "defaults to
a using a case-insensitive filesystem".
> Yes, you _can_ change the setting. No, most don't. Yes, the
> effect is...
> you guessed it: the same as if they did not allow case sensitivity
> at all.
While I agree that most just accept the default, your argument here
and in your previous email is spurious; it amounts to saying "A and B
is offered, but because A is the default it is the same as if B were
not supported at all", which isn't valid logic. If you limited your
argument to criticizing case-insensitive filesystems then I would
have to agree with you; I am not a fan of them. Likewise, if you said
that the default has undesirable consequences I would also concur.
It's your attempt to extend your claim to an argument for equivalence
that I can't buy.
> Plenty of people have this setup
Agreed...
> and we have to suffer.
but, don't you think you're exaggerating a bit here? How much
"suffering" has this really caused you? I gather that you're not even
a user of that operating system; I am (have been since the first
developer previews), have always accepted the default filesystem
choice, don't even like the filesystem (have ranted repeatedly about
its flakiness on my weblog), but I think I've run into case-
insensitivity issues two times. If you want to talk about "suffering"
then ask me about HFS+ data integrity.
Cheers,
Wincent
next parent reply other threads:[~2007-08-29 9:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3f4fd2640708280117k3f1cd03el676a87084a83480f@mail.gmail.com>
[not found] ` <46D3ED4E.6030606@op5.se>
[not found] ` <82tzqjgbx0.fsf@mid.bfk.de>
[not found] ` <5A2EFA05-7A86-440B-B027-6360DA04CD89@wincent.com>
[not found] ` <46D42C07.50001@op5.se>
[not found] ` <54CFD615-6E05-42AC-A0D7-063B146295B8@wincent.com>
[not found] ` <Pine.LNX.4.64.0708282144250.28586@racer.site>
[not found] ` <301B4A5B-1765-426E-B72C-F6248894A3E0@wincent.com>
[not found] ` <Pine.LNX.4.64.0708290321530.28586@racer.site>
2007-08-29 9:31 ` Wincent Colaiuta [this message]
2007-08-29 9:43 ` git: cannot rename foo to Foo on a case-insensitive filesystem (e.g. on Windows) David Kastrup
2007-08-29 10:04 ` Wincent Colaiuta
2007-08-29 10:00 ` Andreas Ericsson
[not found] ` <3f4fd2640708280317o2cee8ae9j28a92f39d8e6a583@mail.gmail.com>
[not found] ` <alpine.LFD.0.999.0708281522260.25853@woody.linux-foundation.org>
[not found] ` <85mywbb7p7.fsf@lola.goethe.zz>
[not found] ` <alpine.LFD.0.999.0708281555580.25853@woody.linux-foundation.org>
2007-09-02 0:20 ` Nix
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1BA15C6C-1F37-401B-B8D8-4BD147CF5225@wincent.com \
--to=win@wincent.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=ae@op5.se \
--cc=fweimer@bfk.de \
--cc=git@vger.kernel.org \
--cc=msclrhd@googlemail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).