From: torvalds@transmeta.com (Linus Torvalds)
To: linux-kernel@vger.kernel.org
Subject: Re: 2.5.2-pre2 forces ramfs on
Date: Wed, 26 Dec 2001 04:17:11 +0000 (UTC) [thread overview]
Message-ID: <a0bj07$18l$1@penguin.transmeta.com> (raw)
In-Reply-To: <2452.1009338062@ocs3.intra.ocs.com.au>
In article <2452.1009338062@ocs3.intra.ocs.com.au>,
Keith Owens <kaos@ocs.com.au> wrote:
>
>Why is ramfs forced on?
Because it's small, and if it wasn't there, we'd have to have the small
"rootfs" anyway (which basically duplicated ramfs functionality).
>And why is Al Viro's email address not in CREDITS or MAINTAINERS? We
>should have somewhere to complain to ;).
He didn't want to be in either file at some point (yes, I asked him),
some day I'll put him in anyway (he's been the effective maintainer of
the VFS interface for the last year or so, regardless of whether he
wants to be in the MAINTAINTERS file or not).
Linus
next prev parent reply other threads:[~2001-12-26 4:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-26 3:41 2.5.2-pre2 forces ramfs on Keith Owens
2001-12-26 4:17 ` Linus Torvalds [this message]
2001-12-26 15:04 ` Alan Cox
2001-12-26 17:20 ` Legacy Fishtank
2001-12-26 17:36 ` Alexander Viro
2001-12-26 17:52 ` Legacy Fishtank
2001-12-27 10:39 ` Christoph Rohland
2002-01-05 22:35 ` Eric W. Biederman
2001-12-26 22:04 ` Linus Torvalds
2001-12-26 4:26 ` Alexander Viro
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='a0bj07$18l$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