From: "Maciej Sołtysiak" <pysiak.satriani@wp.pl>
To: reiserfs-list@namesys.com
Subject: Re: future r4 maintenance question
Date: Sat, 22 Jul 2006 22:04:39 +0200 [thread overview]
Message-ID: <16810401141.20060722220439@wp.pl> (raw)
In-Reply-To: <1153594386.6659.172.camel@ipso.snappymail.ca>
Hello Mike,
Saturday, July 22, 2006, 8:53:06 PM, you wrote:
> I don't understand the concerns here? Kernel v2.4 is essentially in
> "bug-fix only" mode right now, yet I don't see many people complaining
> that the kernel developers have abandoned it. I personally think its
> crazy to expect major features be back ported to old versions.
> For as long as I've been alive programmers have released a major version
> of their software, and only maintained it with minor version bug fixes
> while they work on the next major version to introduce features to it.
> Hans himself has pretty much followed that same path with ReiserFS V3,
> and now V4. There just happened to be a several year gap in between.
Well, that's completely clear. However, reiserfs has had a different situation:
during the bugfix mode, important functionality was beeing added to other
filesystems: extended attribute support, data=ordered, data=journaled.
Reiserfs v3 had noone but Chris Mason (outside of namesys) to do it.
The issue is that reiser4 users should never again feel abandoned like they
did with reiserfs v3. Well, actually a lot of people did not feel it or they
hadn't known about the state of things. Note that back then reiser4 was
basically vapourware if I may say so.
Concluding, I am not here to point anything bad, I am looking adoption-stoppers
for reiser4.
BTW, have Mark Shuttleworth and Hans had a talk about support/sponsorship/ubuntu
endorsement/anything? (i know it may be absolutely private stuff, sorry for asking
if this is the case)
--
Best regards,
Maciej
next prev parent reply other threads:[~2006-07-22 20:04 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 [this message]
2006-07-22 19:32 ` David Masover
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=16810401141.20060722220439@wp.pl \
--to=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.