From: Daniel Phillips <phillips@bonn-fries.net>
To: Steve Lord <lord@sgi.com>, Andreas Dilger <adilger@turbolabs.com>
Cc: "Dennis, Jim" <jdennis@snapserver.com>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: Congrats Marcelo,
Date: Mon, 25 Feb 2002 00:39:36 +0100 [thread overview]
Message-ID: <E16f8Ey-0002qn-00@starship.berlin> (raw)
In-Reply-To: <2D0AFEFEE711D611923E009027D39F2B153AD4@cdserv.meridian-data.com> <20020226140644.U12832@lynx.adilger.int> <1014760581.5993.159.camel@jen.americas.sgi.com>
In-Reply-To: <1014760581.5993.159.camel@jen.americas.sgi.com>
On February 26, 2002 10:56 pm, Steve Lord wrote:
> On Tue, 2002-02-26 at 15:06, Andreas Dilger wrote:
> > On Feb 26, 2002 12:38 -0800, Dennis, Jim wrote:
> > > Now I need to know about the status of several unofficial patches:
> >
> > While my word is by no means official, my general understanding is:
> >
> > > XFS
> >
> > Not for 2.4 - just too many changes to the core kernel code.
>
> Someone has got to kill this assumption people have about XFS, it
> makes much smaller changes than some things which have gone in,
> the odd VM rewrite here and there to name some. Given that we now
> have official EA system calls, the last chunk of stuff to resolve
> is quota. This is being worked on with Jan Kara.
I'd really like to see XFS go in, but don't you think 2.5 is the place,
with a view to 2.4 submission in due course?
As far as making the case goes, do you have time to make a list of
places where XFS goes outside fs/xfs, and why?
--
Daniel
next prev parent reply other threads:[~2002-02-26 22:46 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-26 20:38 Dennis, Jim
2002-02-26 20:50 ` H. Peter Anvin
2002-02-26 21:06 ` Andreas Dilger
2002-02-26 21:15 ` crypto (was Re: Congrats Marcelo,) Jeff Garzik
2002-02-26 22:33 ` Rik van Riel
2002-02-27 21:15 ` Michael H. Warfield
2002-02-27 21:57 ` Rik van Riel
2002-02-27 22:29 ` Michael H. Warfield
2002-02-27 23:06 ` Rik van Riel
2002-02-26 21:35 ` Robert Love
2002-02-26 21:40 ` arjan
2002-02-26 21:47 ` Robert Love
2002-02-24 23:51 ` Daniel Phillips
2002-02-28 22:32 ` Bill Davidsen
2002-03-01 9:50 ` Francois Romieu
2002-02-27 9:41 ` Francois Romieu
2002-02-26 21:56 ` Congrats Marcelo, Steve Lord
2002-02-24 23:39 ` Daniel Phillips [this message]
2002-02-26 23:23 ` Rainer Ellinger
2002-02-25 0:38 ` Daniel Phillips
2002-02-26 23:59 ` Martin J. Bligh
2002-02-27 0:47 ` Rainer Ellinger
2002-02-27 1:08 ` Matthew D. Pitts
2002-02-27 1:03 ` Martin J. Bligh
2002-02-26 22:59 ` Alan Cox
2002-02-26 22:59 ` Steve Lord
2002-02-25 0:28 ` Whither XFS? (was: Congrats Marcelo) Daniel Phillips
2002-02-26 23:39 ` Steve Lord
2002-02-25 8:22 ` Daniel Phillips
2002-02-26 23:00 ` Congrats Marcelo, J.A. Magallon
2002-02-26 23:07 ` Steve Lord
2002-02-25 0:10 ` Daniel Phillips
2002-02-28 21:52 ` Marcelo Tosatti
2002-03-01 0:01 ` Alan Cox
2002-03-01 0:37 ` Dave Jones
2002-03-01 1:13 ` Alan Cox
2002-03-01 1:03 ` Dave Jones
2002-03-01 1:51 ` Alan Cox
2002-03-01 1:28 ` Theodore Tso
2002-03-01 1:53 ` Mike Fedyk
2002-03-02 22:35 ` Hans-Peter Jansen
2002-03-02 3:43 ` Stephen Degler
2002-02-28 22:41 ` Bill Davidsen
2002-03-01 9:30 Andries.Brouwer
2002-03-01 18:33 ` Mike Fedyk
2002-03-02 4:13 Dennis, Jim
2002-03-02 18:24 ` David Ford
2002-03-03 22:58 ` Florian Weimer
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=E16f8Ey-0002qn-00@starship.berlin \
--to=phillips@bonn-fries.net \
--cc=adilger@turbolabs.com \
--cc=jdennis@snapserver.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lord@sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®