public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Albert Cahalan <albert@users.sf.net>
To: Dan Kegel <dank@kegel.com>
Cc: Sam Ravnborg <sam@ravnborg.org>,
	linux-kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: Building on case-insensitive systems
Date: 17 Oct 2004 15:54:56 -0400	[thread overview]
Message-ID: <1098042896.2669.14306.camel@cube> (raw)
In-Reply-To: <4172A8FD.8000401@kegel.com>

On Sun, 2004-10-17 at 13:16, Dan Kegel wrote:
> Albert Cahalan wrote:
> >>>>You are betting that you can force developers to switch away
> >>>>from Windows and MacOSX workstations.
> >>>
> >>>Actually, I'm betting that "required to build product"
> >>>is a magic phrase that overrides corporate IT's desire
> >>>to brutally enforce a Microsoft-only environment.
> >>
> >>Seems you are not part of one of these organisations.
> >>That argument will not suffice.
> > 
> > I was, twice, and it did suffice. Try it:
> > 
> > "needed for revenue generation"
> > "required to meet customer needs"
> > ...
> > 
> > Don't be taking away the ammo.
> > 
> > When the argument doesn't work, your organization
> > is obviously not fully committed to making a profit.
> > Politics are getting in the way. It's OK though,
> > since that just puts you at a market disadvantage.
> > Soon enough, the competiter will be hiring.
> 
> "Politics are just getting in the way"?
> Boy, that's the pot calling the kettle black...

Hey, fight fire with fire.

The ".s" suffix is deeply rooted in tradition.

Since MacOS can handle case-sensitive UFS filesystems,
and it has just been reported that Microsoft SFU also
supports being case-sensitive, the problem is solved.
The only change needed is the way a library is linked.

Bummer, actually.



  reply	other threads:[~2004-10-17 20:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-17  5:06 Building on case-insensitive systems Albert Cahalan
2004-10-17  4:38 ` Dan Kegel
2004-10-17  5:43   ` Albert Cahalan
2004-10-17  9:27     ` Sam Ravnborg
2004-10-17  9:05       ` Anand Kumria
2004-10-17 16:41       ` Denis Vlasenko
2004-10-17 17:55       ` Albert Cahalan
2004-10-17 17:16         ` Dan Kegel
2004-10-17 19:54           ` Albert Cahalan [this message]
2004-10-17 19:34             ` Dan Kegel
     [not found] <fa.e78dm07.jjs3q5@ifi.uio.no>
     [not found] ` <fa.e17vks0.10kojhi@ifi.uio.no>
2004-10-17 12:19   ` Bodo Eggert

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=1098042896.2669.14306.camel@cube \
    --to=albert@users.sf.net \
    --cc=dank@kegel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.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