From: "Bones" <bones10@msn.com>
To: <linux-xfs@oss.sgi.com>
Subject: RE: Tomorrow 
Date: Mon, 26 May 2003 22:33:06 -0600
Message-ID: <JHEILHKOJAMNODABOOOAEEGDCKAA.bones10@msn.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <200305270323.h4R3N4nE061863@elmo.melbourne.sgi.com>
Importance: Normal
Sender: linux-xfs-bounce@oss.sgi.com
Errors-to: linux-xfs-bounce@oss.sgi.com
Precedence: bulk
Content-Length: 1221
Lines: 37

I'm just curious, is the case insensitivity work being done starting with
what I sent a while back?

If so, I've fixed some things in that code, that you'd want to have before
you get too far along.

- bones

-----Original Message-----
From: linux-xfs-bounce@oss.sgi.com
[mailto:linux-xfs-bounce@oss.sgi.com]On Behalf Of Daniel Moore
Sent: Monday, May 26, 2003 9:23 PM
To: linux-xfs@oss.sgi.com
Subject: Re: Tomorrow


Ethan Benson writes:

 => so long as it can be turned off at compile time, and the broken
 => behavior is never default im happy.  still would rather see you guys
 => working on more important things.=20

It's obviously more important than you think or else we wouldn't
be working on it... No one is remotely interested in making it
default anywhere - it's an extra feature that will be extremely
useful in certain specific situations and provide much better
performance in those situations than any user space hack could
provide.

-------------------------------------------------------
 Daniel Moore                    dxm@sgi.com
 R&D Software Engineer           Phone: +61-3-98348209
 SGI Australian Software Group   Fax:   +61-3-98132378
-------------------------------------------------------