From: David Masover <ninja@slaphack.com>
To: Pysiak Satriani <pysiak.satriani@wp.pl>
Cc: "reiserfs-list@namesys.com" <reiserfs-list@namesys.com>
Subject: Re: future r4 maintenance question
Date: Sat, 22 Jul 2006 14:32:47 -0500 [thread overview]
Message-ID: <44C27D5F.3040405@slaphack.com> (raw)
In-Reply-To: <1992401892.20060722173244@wp.pl>
Pysiak Satriani wrote:
> Hello,
>
> one of the concerns of LKML folks about r4 is that namesys after
> finishing their work with r4 will "rush off" to reiser5 leaving
> r4 as "stable" in a "bugfix-mode only"
> But a question arises. Will namesys keep r4 in a bugfix-only mode
> (as with reiserfs v3) or will it have resources planned not only
> for bugfixes but for updates too ?
As I understand it, r4 is currently not finished, especially comparing
the whitepaper with reality. So, while the features that are finished
are mostly stable, I can't imagine them rushing off to v5 without
finishing the features originally planned for v4.
Examples would be pseudofiles, custom plugins (per-file and
per-directory, also), a repacker, fsync optimization, a
crypto/compression plugin...
Ultimately, this may happen, but by then, I expect v4 would be fairly
stable and complete. Besides, bugfix-only does imply bugfixes, which is
about all most other filesystems get these days...
Disclaimer: I don't work here. If you want a definitive answer, wait
for someone at Namesys to confirm or deny what I've just said.
prev parent reply other threads:[~2006-07-22 19:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-22 15:32 future r4 maintenance question Pysiak Satriani
2006-07-22 18:03 ` Hans Reiser
2006-07-22 19:51 ` Maciej Sołtysiak
2006-07-22 20:16 ` David Masover
2006-07-22 21:26 ` Maciej Sołtysiak
2006-07-23 6:23 ` Hans Reiser
2006-07-23 6:07 ` Hans Reiser
2006-07-22 18:53 ` Mike Benoit
2006-07-22 19:12 ` Matthias Barremaecker
2006-07-22 19:42 ` David Masover
2006-07-23 11:11 ` Sander Sweers
2006-07-22 20:04 ` Maciej Sołtysiak
2006-07-22 19:32 ` David Masover [this message]
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=44C27D5F.3040405@slaphack.com \
--to=ninja@slaphack.com \
--cc=pysiak.satriani@wp.pl \
--cc=reiserfs-list@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.