From: Jens Axboe <axboe@suse.de>
To: Robert Love <rml@tech9.net>
Cc: Anuradha Ratnaweera <anuradha@gnu.org>, linux-kernel@vger.kernel.org
Subject: Re: Why XFS not in the main kernel?
Date: Tue, 23 Oct 2001 08:44:33 +0200 [thread overview]
Message-ID: <20011023084433.D638@suse.de> (raw)
In-Reply-To: <20011023113546.A1310@bee.lk> <1003818066.1491.2.camel@phantasy>
In-Reply-To: <1003818066.1491.2.camel@phantasy>
On Tue, Oct 23 2001, Robert Love wrote:
> On Tue, 2001-10-23 at 01:35, Anuradha Ratnaweera wrote:
> > Is there a reason not to include XFS in the mainstream kernel? It
> > is very stable and many (including us) are using it in production
> > environments without problems.
> >
> > Obviously, there can't be liscening issues, because XFS is released
> > under GPL.
>
> No one doubts XFS is stable. It is a great fs. But XFS includes some
> modifications to block layer and such that people aren't ready to
Not really the block layer -- this used to be the case. SGI kiobuf block
stuff was too ugly to live, and consequently it even died within the XFS
tree :)
--
Jens Axboe
prev parent reply other threads:[~2001-10-23 6:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-23 5:35 Why XFS not in the main kernel? Anuradha Ratnaweera
2001-10-23 6:21 ` Robert Love
2001-10-23 6:44 ` Jens Axboe [this message]
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=20011023084433.D638@suse.de \
--to=axboe@suse.de \
--cc=anuradha@gnu.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.net \
/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