From: Aaron Lehmann <aaronl@vitelus.com>
To: Linus Torvalds <torvalds@transmeta.com>, linux-kernel@vger.kernel.org
Subject: Re: Does reiserfs really meet the "Linux-2.4.x patch submission policy"?
Date: Tue, 16 Jan 2001 17:05:39 -0800 [thread overview]
Message-ID: <20010116170539.A3497@vitelus.com> (raw)
In-Reply-To: <937neu$p95$1@penguin.transmeta.com> <20010116205558.A1171@sm.luth.se>
In-Reply-To: <20010116205558.A1171@sm.luth.se>; from anedah-9@sm.luth.se on Tue, Jan 16, 2001 at 08:55:58PM +0100
[-- Attachment #1: Type: text/plain, Size: 528 bytes --]
On Tue, Jan 16, 2001 at 08:55:58PM +0100, Andr? Dahlqvist wrote:
> I was very surprised when I checked my local kernel.org mirror this
> morning, and noticed that the latest 2.4.1 pre-patch had grown to
> ~180 kb in size. I was even more surprised when I realized that the
> inclusion of reiserfs was the reason for this.
On a related note, how about XFS? It certainly shouldn't go in before
the developers are ready, but I've been using it without any problems
for awhile now and await its inclusion in the mainstream kernel.
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2001-01-17 1:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-06 18:17 Linux-2.4.x patch submission policy Linus Torvalds
2001-01-06 19:33 ` Alan Cox
2001-01-06 20:12 ` Linux-2.4.x patch submission policy (what about the -AC series?) Ben Greear
2001-01-07 16:37 ` Linux-2.4.x patch submission policy Rik van Riel
2001-01-08 21:33 ` Ingo Oeser
2001-01-08 20:40 ` Rik van Riel
2001-01-10 11:12 ` Roeland Th. Jansen
2001-01-16 19:55 ` Does reiserfs really meet the "Linux-2.4.x patch submission policy"? André Dahlqvist
2001-01-16 20:25 ` Linus Torvalds
2001-01-17 1:05 ` Aaron Lehmann [this message]
2001-01-17 1:14 ` Linus Torvalds
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=20010116170539.A3497@vitelus.com \
--to=aaronl@vitelus.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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