All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Ericsson <ae@op5.se>
To: Wincent Colaiuta <win@wincent.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	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 12:00:09 +0200	[thread overview]
Message-ID: <46D543A9.3050105@op5.se> (raw)
In-Reply-To: <1BA15C6C-1F37-401B-B8D8-4BD147CF5225@wincent.com>

Wincent Colaiuta wrote:
> El 29/8/2007, a las 4:23, Johannes Schindelin escribió:
> 
>>
>> 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.
> 

My original comment was in error. I was unaware that Apple shipped
different filesystems and that there was actually a choice. Me having
sat by a friend who did his installation didn't realize I had the option
of using a case-sensitive filesystem, so I assumed it wasn't there, which
only goes to show that assumption indeed is the mother of all fuckups. Not
wanting a pointless discussion in which everyone agrees in spirit but
nitpicks about factual details, I didn't respond to any of the posts.

Since it seems we all agree that case-insensitive, case-reporting file-
systems are disgusting and it's now thoroughly proven that Apple does
indeed ship a proper filesystem with its OS X releases, can we please
drop this now and move on to trying to improve things? I'll take
universal silence on the subject as "good idea, let's do that"

> 
>> and we have to suffer.
> 
> but, don't you think you're exaggerating a bit here? How much 
> "suffering" has this really caused you?

Plenty enough, I should imagine. As David Kastrup mentioned, Dscho
does extensive work on MSYS/MingW while not using it himself.

Besides that, there are all these timeconsuming threads that some
ignorant dumbass (in this case me) turn into silly pie-fights with
some uninformed remark that is overly tainted by personal opinion.

My apologies. I shall do my research better in the future.

-- 
Andreas Ericsson                   andreas.ericsson@op5.se
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231

  parent reply	other threads:[~2007-08-29 10:00 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                 ` git: cannot rename foo to Foo on a case-insensitive filesystem (e.g. on Windows) Wincent Colaiuta
2007-08-29  9:43                   ` David Kastrup
2007-08-29 10:04                     ` Wincent Colaiuta
2007-08-29 10:00                   ` Andreas Ericsson [this message]
     [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

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

  git send-email \
    --in-reply-to=46D543A9.3050105@op5.se \
    --to=ae@op5.se \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=fweimer@bfk.de \
    --cc=git@vger.kernel.org \
    --cc=msclrhd@googlemail.com \
    --cc=win@wincent.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.
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.