From: Hans Reiser <reiser@namesys.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Vladimir Saveliev <vs@namesys.com>, linux-kernel@vger.kernel.org
Subject: ReiserFS V4 (was Re: 2.6.2-rc3-mm1)
Date: Tue, 03 Feb 2004 15:21:59 -0800 [thread overview]
Message-ID: <40202D17.1000904@namesys.com> (raw)
In-Reply-To: <20040203010456.3f3a2618.akpm@osdl.org>
Andrew Morton wrote:
>
>Be aware that the barriers for a new filesystem are relatively high: each
>one adds a significant maintenance burden to the VFS and MM developers. It
>will need cautious review.
>
>
Andrew, while it is your decision to make, it would be very silly to not
let us upgrade ReiserFS. V4 is 2-5x the speed of V3, has more
functionality, better security, is more maintainable, etc. Once V4 is
as stable and tested as V3, no one in their right mind will use V3 on a
new install. While we will be happy to read improvements and critiques
of our implementations from a clever coder such as yourself, we aren't
exactly new to the Linux Kernel, and we are one of the very few in that
community who have a real QA process that we systematically apply. That
is why we did not send it in many months ago: our testing is quite
extensive, and we don't think users should find bugs that we can find if
we make the effort. Now we are running out of bugs that we can hit.
There are distros that would like to ship using Reiser4 in April.
>But that doesn't mean we cannot get it out there, get you some more testing
>and exposure.
>-
>
>
>
Thanks,
Hans
next prev parent reply other threads:[~2004-02-03 23:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-03 7:58 2.6.2-rc3-mm1 Andrew Morton
2004-02-03 8:52 ` 2.6.2-rc3-mm1 Vladimir Saveliev
2004-02-03 9:04 ` 2.6.2-rc3-mm1 Andrew Morton
2004-02-03 23:21 ` Hans Reiser [this message]
2004-02-04 12:00 ` ReiserFS V4 (was Re: 2.6.2-rc3-mm1) Tomas Szepe
2004-02-04 15:24 ` Hans Reiser
2004-02-03 9:58 ` 2.6.2-rc3-mm1 Prakash K. Cheemplavam
2004-02-03 10:10 ` 2.6.2-rc3-mm1 Prakash K. Cheemplavam
2004-02-03 10:16 ` 2.6.2-rc3-mm1 Helge Hafting
2004-02-03 10:33 ` 2.6.2-rc3-mm1 Andrew Morton
2004-02-03 17:39 ` 2.6.2-rc3-mm1 Alistair John Strachan
2004-02-03 18:32 ` 2.6.2-rc3-mm1 Bartlomiej Zolnierkiewicz
2004-02-03 23:47 ` 2.6.2-rc3-mm1 Alistair John Strachan
2004-02-04 0:00 ` 2.6.2-rc3-mm1 Bartlomiej Zolnierkiewicz
2004-02-04 0:17 ` 2.6.2-rc3-mm1 Alistair John Strachan
2004-02-04 0:35 ` 2.6.2-rc3-mm1 Bartlomiej Zolnierkiewicz
2004-02-04 1:03 ` 2.6.2-rc3-mm1 Alistair John Strachan
2004-02-04 1:29 ` 2.6.2-rc3-mm1 Bartlomiej Zolnierkiewicz
[not found] ` <Pine.LNX.4.58.0402031941560.665@uberdeity>
2004-02-04 10:05 ` 2.6.2-rc3-mm1 Alistair John Strachan
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=40202D17.1000904@namesys.com \
--to=reiser@namesys.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vs@namesys.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