From: Hans Reiser <reiser@namesys.com>
To: David Lang <david.lang@digitalinsight.com>
Cc: Ed Tomlinson <tomlins@cam.org>, Ed Cogburn <edcogburn@hotpop.com>,
linux-kernel@vger.kernel.org
Subject: Re: reiser4 vs politics: linux misses out again
Date: Sat, 09 Jul 2005 00:23:47 -0700 [thread overview]
Message-ID: <42CF7B83.9000804@namesys.com> (raw)
In-Reply-To: <Pine.LNX.4.62.0507081737120.4458@qynat.qvtvafvgr.pbz>
David Lang wrote:
>
> remember that Hans is on record (over a year ago) arguing that R3
> should not be fixed becouse R4 was replacing it.
No, I said and say that V3 should not have features added to it, because
features should not be added to a stable branch. Bug fixes are good.
There are a few V3 bug fixes where the fix is so deep that it belongs in
V4, all of the ones that I can think of at the moment are ones requiring
disk format changes.
Note that in V4, disk format changes are no longer deep fixes because of
plugins.
>
> This type of thing is one of the reasons that you see arguments that
> aren't 'purely code-related' becouse the kernel folks realize that
> _they_ will have to maintain the code over time, Hans and company will
> go on and develop R5 (R10, whatever) and consider R4 obsolete and stop
> maintaining it.
No, we will stop adding features to it at some point, only add bug
fixes, and let it become stable enough for mission critical use. Of
course, with plugins this becomes more complicated of a policy because
smaller releases with more orthogonal features are easier and more
tempting, and it becomes tempting to version and release plugins rather
than the FS, so I am not sure exactly how this will play out yet. I
think we will have an option to select experimental plugins individually.
>
> David Lang
>
next prev parent reply other threads:[~2005-07-09 7:24 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-30 12:26 reiser4 vs politics: linux misses out again shevek
2005-06-30 9:44 ` Christopher Warner
2005-06-30 12:45 ` Rik Van Riel
2005-06-30 12:53 ` Richard B. Johnson
2005-06-30 20:21 ` Bill Davidsen
2005-07-01 20:54 ` James Courtier-Dutton
2005-06-30 15:33 ` Jim Crilly
2005-06-30 16:02 ` Markus Törnqvist
2005-06-30 18:10 ` Jim Crilly
2005-07-02 13:05 ` Ed Cogburn
2005-07-02 14:59 ` Christoph Hellwig
2005-07-03 22:34 ` Ed Cogburn
2005-07-02 21:56 ` Jim Crilly
2005-07-03 23:30 ` Ed Cogburn
2005-07-04 1:13 ` Jim Crilly
2005-07-04 1:25 ` Ed Cogburn
2005-07-04 2:11 ` Horst von Brand
2005-07-05 19:44 ` cutaway
2005-07-08 22:59 ` Ed Cogburn
2005-07-09 0:26 ` Ed Tomlinson
2005-07-09 0:39 ` David Lang
2005-07-09 3:25 ` Ed Cogburn
2005-07-09 21:40 ` David Lang
2005-07-10 5:10 ` Horst von Brand
2005-07-10 12:48 ` Ed Tomlinson
2005-07-10 16:06 ` Alexey Dobriyan
2005-07-10 20:21 ` Jim Crilly
2005-07-11 0:01 ` Ed Cogburn
2005-07-11 0:13 ` David Lang
2005-07-11 0:18 ` Jim Crilly
2005-07-11 2:43 ` Ed Cogburn
2005-07-11 2:40 ` Jim Crilly
2005-07-11 11:09 ` Ed Tomlinson
2005-07-11 18:16 ` Jim Crilly
2005-07-11 19:07 ` Hans Reiser
2005-07-11 1:12 ` Hans Reiser
2005-07-11 9:01 ` Erik Hensema
2005-07-11 18:15 ` Horst von Brand
2005-07-11 19:04 ` Hans Reiser
2005-07-11 20:40 ` Erik Hensema
2005-07-09 7:23 ` Hans Reiser [this message]
2005-07-04 6:50 ` Jens Axboe
2005-07-04 13:42 ` Maciej Soltysiak
2005-07-04 1:35 ` Horst von Brand
2005-07-01 4:08 ` Miles Bader
-- strict thread matches above, loose matches on Subject: below --
2005-06-30 15:27 Markus Törnqvist
2005-06-30 22:37 Parag Warudkar
2005-07-01 11:29 ` Richard B. Johnson
2005-07-01 11:43 ` Luigi Genoni
2005-07-01 12:17 ` Richard B. Johnson
2005-07-01 12:30 ` Luigi Genoni
2005-07-01 15:27 arjun kumar
2005-07-01 15:44 ` Artem B. Bityuckiy
2005-07-01 15:55 ` Schneelocke
2005-07-01 15:59 ` arjun kumar
2005-07-01 15:53 Parag Warudkar
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=42CF7B83.9000804@namesys.com \
--to=reiser@namesys.com \
--cc=david.lang@digitalinsight.com \
--cc=edcogburn@hotpop.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tomlins@cam.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