From: "R. J. Wysocki" <rjwysocki@sisk.pl>
To: Sean Neakums <sneakums@zork.net>, linux-kernel@vger.kernel.org
Subject: Re: Collapse ext2 and 3 please
Date: Fri, 25 Jun 2004 23:36:50 +0200 [thread overview]
Message-ID: <200406252336.50522.rjwysocki@sisk.pl> (raw)
In-Reply-To: <6u8yeb1hwc.fsf@zork.zork.net>
On Friday 25 of June 2004 22:50, Sean Neakums wrote:
> "R. J. Wysocki" <rjwysocki@sisk.pl> writes:
> > I think that the good reason for keeping both ext* code bases in the
> > kernel tree is that _there_ _are_ _some_ people who will need ext2 for
> > some purposes, so why should we pull the carpet from under them?
>
> An ext3 that supports no-journal operation can surely register itself
> as both ext2 and ext3 and leave userspace none the wiser.
>
> I don't think anybody wants to pull any carpets out from under anyone.
Sorry, I've been too offensive.
IMO, if ext2 is kept separate, the development of it may be focused on
different user needs than the development of ext3 is focused on. It's worth
doing as long as there's someone who will prefer ext2 to ext3 and someone
who's interested in working on ext2 itself. That's my point.
Yours,
rjw
----------------------------
For a successful technology, reality must take precedence over public
relations, for nature cannot be fooled.
-- Richard P. Feynman
next prev parent reply other threads:[~2004-06-25 21:28 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-24 23:14 John Richard Moser
2004-06-25 9:16 ` Helge Hafting
2004-06-25 11:30 ` David van Hoose
2004-06-25 11:41 ` Christoph Hellwig
2004-06-25 11:50 ` David van Hoose
2004-06-25 12:01 ` Matthew Garrett
[not found] ` <1088165028.16286.59.camel@imp.csi.cam.ac.uk>
2004-06-25 12:05 ` David van Hoose
2004-06-25 12:13 ` Matthew Garrett
[not found] ` <1088165426.16286.67.camel@imp.csi.cam.ac.uk>
2004-06-25 12:18 ` David van Hoose
2004-06-25 13:03 ` Tigran Aivazian
2004-06-25 12:40 ` David van Hoose
2004-06-25 14:03 ` Rik van Riel
2004-06-25 12:10 ` Christoph Hellwig
2004-06-25 12:15 ` David van Hoose
2004-06-25 12:26 ` Richard B. Johnson
2004-06-25 12:48 ` Philip R. Auld
2004-06-25 12:53 ` David van Hoose
2004-06-25 13:39 ` Tigran Aivazian
2004-06-25 18:55 ` David van Hoose
2004-06-25 22:26 ` John Richard Moser
2004-06-25 12:25 ` Sean Neakums
2004-06-25 18:01 ` Timothy Miller
2004-06-25 18:04 ` Sean Neakums
2004-06-25 18:41 ` Timothy Miller
2004-06-25 20:52 ` R. J. Wysocki
2004-06-25 20:50 ` Sean Neakums
2004-06-25 21:36 ` R. J. Wysocki [this message]
2004-06-25 22:00 ` Andrew Morton
2004-06-25 23:48 ` John Richard Moser
[not found] <2aZfF-3es-5@gated-at.bofh.it>
[not found] ` <2b45V-6tl-39@gated-at.bofh.it>
2004-06-25 22:28 ` Pascal Schmidt
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=200406252336.50522.rjwysocki@sisk.pl \
--to=rjwysocki@sisk.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=sneakums@zork.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
all inboxes | Powered by JetHome®