public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: torvalds@transmeta.com (Linus Torvalds)
To: linux-kernel@vger.kernel.org
Subject: Re: Linux-2.4.10 + ext3
Date: Mon, 24 Sep 2001 18:12:01 +0000 (UTC)	[thread overview]
Message-ID: <9ont1h$5fl$1@penguin.transmeta.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0109231142060.1078-100000@penguin.transmeta.com> <1001280620.3540.33.camel@gromit.house> <9om4ed$1hv$1@penguin.transmeta.com> <20010923193008.A13982@vitelus.com>

In article <20010923193008.A13982@vitelus.com>,
Aaron Lehmann  <aaronl@vitelus.com> wrote:
>On Mon, Sep 24, 2001 at 02:06:05AM +0000, Linus Torvalds wrote:
>> We'll merge ext3 soon enough.. As RH seems to start using it more and
>> more, there's more reason to merge it into the standard kernel too.
>> 
>> So don't worry. It will happen.
>
>Kinda OT, but ext3 is often treated more like a new file system than
>an extension of ext2. I'm wondering if this is a good thing. On the
>machines where I use it I have to compile both ext3 and ext2 (because
>it would be foolish to not have ext2 support) into the kernel.

Well, for one thing I absolutely refused during ext3 development to have
ext3 just be an "extension" to ext2. That _was_ how it was originally
thought of, and I very much wanted ext3 to be separate - I strongly felt
that it would be stupid to force people who use ext2 for "stable"
reasons to have to get the extensions (and I hate #ifdef's).

And quite frankly, I don't think we _still_ are at the point where I'd
be comfortable saying that we could just merge them, and everybody would
use the superset of the code.

In five years maybe nobody has any stability worries at all about ext3
code, and we can just drop ext2 and consider it purely a backwards
compatibility extension of ext3.

		Linus

  parent reply	other threads:[~2001-09-24 18:14 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-23 18:54 Linux-2.4.10 Linus Torvalds
2001-09-23 16:41 ` Linux-2.4.10 Rob Landley
2001-09-23 21:32   ` Linux-2.4.10 André Dahlqvist
2001-09-23 21:54   ` Linux-2.4.10 Alan Cox
2001-09-23 21:30 ` Linux-2.4.10 + ext3 Michael Rothwell
2001-09-23 22:18   ` Gergely Nagy
2001-09-24  2:06   ` Linus Torvalds
2001-09-24  2:30     ` Aaron Lehmann
2001-09-24  3:45       ` Andrew Morton
2001-09-24  4:35         ` Simon Fowler
2001-09-24 20:40           ` Stephen C. Tweedie
2001-09-24  4:45         ` Aaron Lehmann
2001-09-24  5:19           ` Andrew Morton
2001-09-24 19:49             ` Jamie Lokier
2001-09-24 20:22               ` Chris Meadors
2001-09-24 21:57                 ` Jamie Lokier
2001-09-24 21:04               ` Andreas Dilger
2001-09-24 18:12       ` Linus Torvalds [this message]
2001-09-24 18:25         ` Alexander Viro
2001-09-26 16:49     ` Stephen C. Tweedie
2001-09-27 12:12       ` Jan Kara
2001-09-27 18:37         ` Stephen C. Tweedie
2001-09-23 21:54 ` Linux-2.4.10 Trond Myklebust
2001-09-23 22:34 ` Linux-2.4.10 David Woodhouse
2001-09-24  6:28   ` Linux-2.4.10 Erik Andersen
2001-09-24  6:48   ` Linux-2.4.10 David Woodhouse
2001-09-24 17:40     ` Linux-2.4.10 Erik Andersen
2001-09-24 17:41     ` Linux-2.4.10 David Woodhouse
2001-09-23 22:40 ` Linux-2.4.10 - necessary patches Eyal Lebedinsky
2001-09-24  0:04   ` Alan Cox
2001-09-24 14:42     ` Oliver Xymoron
2001-09-24  1:25 ` Linux-2.4.10 Matthias Andree
2001-09-24  2:26   ` Linux-2.4.10 Daniel T. Chen
2001-09-24  3:19     ` Linux-2.4.10 Matthias Andree
2001-09-24  2:57   ` Linux-2.4.10 Disconnect
2001-09-24 10:07     ` Linux-2.4.10 Matthias Andree
2001-09-27 12:17     ` Linux-2.4.10 Roeland Th. Jansen
2001-09-24  2:35 ` Linux-2.4.10 Naren Devaiah
2001-09-24  9:37 ` PATCH[2.4.9-pre14] Kill *writeonly* variable Martin Dalecki
2001-09-27 15:23 ` Linux-2.4.10 George R. Kasica
2001-09-27 15:27   ` Linux-2.4.10 Rik van Riel
2001-09-27 15:31   ` Linux-2.4.10 Bernd Petrovitsch
2001-09-27 15:49   ` Linux-2.4.10 John Jasen
2001-09-27 18:23   ` Linux-2.4.10 Petr Baudis

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='9ont1h$5fl$1@penguin.transmeta.com' \
    --to=torvalds@transmeta.com \
    --cc=linux-kernel@vger.kernel.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