From: Rudy Zijlstra <rudy@edsons.demon.nl>
To: Hans Reiser <reiser@namesys.com>
Cc: Jeff Mahoney <jeffm@suse.com>,
7eggert@gmx.de, Eric Dumazet <dada1@cosmosbay.com>,
ReiserFS List <reiserfs-list@namesys.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] reiserfs: fix handling of device names with /'s in them
Date: Tue, 18 Jul 2006 00:26:23 +0200 [thread overview]
Message-ID: <44BC0E8F.2090504@edsons.demon.nl> (raw)
In-Reply-To: <44BBFB0D.6040105@namesys.com>
Hans Reiser wrote:
>Jeff Mahoney wrote:
>
>
>
><snip>
>
>
>so why did you take their stable branch away from them by working on
>more than bugfixes for V3?
>
>Jeff, working on v3 at this point is nuts. V4 blows it away....
>
>
Hans,
I appreciate your vision and willingness to work to that vision.
The above though, is pure and simple PR. Please do not confuse PR with
maintenance, or design maintenance.
I run pretty recent kernels on some of my servers and or workstations
(2.6.17.4 at the moment). Some others are still using 2.4. All of them
are using reiserfs3. I use reiser3 for most all, except video
application partitions where XFS is used. For the past 2 yr i have been
really pressed for time, and as a result have needed to scale back on
pet projects, like testing new filesystems which are not yet into
mainline. Once Reiserfs4 gets into mainline, i will test on a
workstation. Till that time (and after) any work done on reiserfs3 is
very much appreciated by me. It is keeping v3 up with changing
requirements and expectations.
You cannot start developing a new version and then quit supporting the
previous version. I consider the work Jeff and others have been doing a
very good maintenance job. YES, a maintenance job. Addition of
relatively minor features is part of normal maintenance.
I expect you to disagree here, i am used to that (having followed
reiserfs list for many years).
Cheers,
Rudy Zijlstra
P.S. reducing maintenance to pure bug-fixing is tentamount to announcing
EOL.
next prev parent reply other threads:[~2006-07-17 22:26 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6xQ4C-6NB-43@gated-at.bofh.it>
[not found] ` <6xQea-6ZX-13@gated-at.bofh.it>
2006-07-14 16:10 ` [PATCH] reiserfs: fix handling of device names with /'s in them Bodo Eggert
2006-07-14 17:50 ` Jeff Mahoney
2006-07-16 7:12 ` Hans Reiser
2006-07-16 15:56 ` Jeffrey Mahoney
2006-07-16 18:14 ` Hans Reiser
2006-07-16 22:17 ` Jeff Mahoney
2006-07-17 1:21 ` Hans Reiser
2006-07-17 1:50 ` Jeffrey Mahoney
2006-07-17 3:02 ` Hans Reiser
2006-07-17 3:17 ` Jeffrey Mahoney
2006-07-17 7:29 ` Hans Reiser
2006-07-17 14:55 ` Jeff Mahoney
2006-07-17 18:19 ` Hans Reiser
2006-07-17 18:38 ` Jeff Mahoney
2006-07-17 19:07 ` Hans Reiser
2006-07-17 19:59 ` Jeff Mahoney
2006-07-17 21:03 ` Hans Reiser
2006-07-17 22:26 ` Rudy Zijlstra [this message]
2006-07-18 0:26 ` Horst von Brand
2006-07-18 16:38 ` Jan Engelhardt
2006-07-18 18:37 ` Pekka Enberg
2006-07-17 18:08 ` Valdis.Kletnieks
2006-07-17 18:16 ` Jeff Mahoney
2006-07-17 18:53 ` Hans Reiser
2006-07-17 19:07 ` Jeff Mahoney
2006-07-17 18:27 ` Hans Reiser
2006-07-17 19:52 ` Valdis.Kletnieks
2006-07-12 16:42 Jeff Mahoney
2006-07-12 16:57 ` Eric Dumazet
2006-07-12 17:02 ` Jeff Mahoney
2006-07-13 0:55 ` Andrew Morton
2006-07-13 3:51 ` Hans Reiser
2006-07-13 4:00 ` Andrew Morton
2006-07-13 7:34 ` Hans Reiser
2006-07-13 5:23 ` H. Peter Anvin
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=44BC0E8F.2090504@edsons.demon.nl \
--to=rudy@edsons.demon.nl \
--cc=7eggert@gmx.de \
--cc=akpm@osdl.org \
--cc=dada1@cosmosbay.com \
--cc=jeffm@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reiser@namesys.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox