public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Denis Vlasenko <vda.linux@googlemail.com>
Cc: reiser@namesys.com, linux-kernel@vger.kernel.org
Subject: Re: reiser4: maybe just fix bugs?
Date: Mon, 31 Jul 2006 14:38:21 +0200	[thread overview]
Message-ID: <20060731123821.GC3658@stusta.de> (raw)
In-Reply-To: <1158166a0607310226m5e134307o8c6bedd1f883479c@mail.gmail.com>

On Mon, Jul 31, 2006 at 10:26:55AM +0100, Denis Vlasenko wrote:

> Hi Hans,
> 
> The reiser4 thread seem to be longer than usual.
> Let me, a mere user, add some input.
> 
> It looks to me that delay with reiser4 acceptance
> is caused by two different things.
> 
> First, reiser4 adds those plugins which many FS people
> see as belonging to VFS layer rather than to particular FS.
> 
> And second, reiser team was a bit lax at fixing bugs.
> Not too bad when compared to other FSes, but still.
> 
> When singled out, none of these things are bad enough to hold off
> inclusion. However, combined impact of _both_ of them
> did upset maintainers enough.
>...

This is a wrong impression.

The bug fixing of reiser4 is definitely better than the average in the 
kernel. If you wanted to get e.g. the SATA drivers removed from the 
kernel, bug handling might be a point in favor of the removal. But 
that's not a problem with reiser4.

[1] tries to give an overview of the actual problems with the reiser4 
inclusion.

> vda

cu
Adrian

[1] http://wiki.kernelnewbies.org/WhyReiser4IsNotIn

-- 

    Gentoo kernels are 42 times more popular than SUSE kernels among
    KLive users  (a service by SUSE contractor Andrea Arcangeli that
    gathers data about kernels from many users worldwide).

       There are three kinds of lies: Lies, Damn Lies, and Statistics.
                                                    Benjamin Disraeli


  reply	other threads:[~2006-07-31 12:38 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-31  9:26 reiser4: maybe just fix bugs? Denis Vlasenko
2006-07-31 12:38 ` Adrian Bunk [this message]
2006-07-31 16:17 ` Horst H. von Brand
2006-07-31 20:06   ` Denis Vlasenko
2006-08-01 15:22     ` Theodore Tso
2006-08-01  2:30 ` Hans Reiser
2006-08-01 10:37   ` Pavel Machek
2006-08-01 13:59     ` Scott J. Harmon
2006-08-02  6:22       ` Jan Engelhardt
2006-08-02 19:53   ` Denis Vlasenko
2006-08-01  8:31 ` Andrew Morton
2006-08-01  2:18   ` Hans Reiser
2006-08-01 11:24     ` Vladimir V. Saveliev
2006-08-01 14:33       ` Andrew Morton
2006-08-01 15:07         ` Vladimir V. Saveliev
2006-08-01 16:55           ` David Masover
2006-08-01 19:26             ` Nate Diller
2006-08-02  3:54               ` David Masover
2006-08-03  7:46             ` Theodore Tso
2006-08-04 21:09               ` David Masover
2006-08-01 19:14         ` Nate Diller
2006-08-01 11:43   ` Christoph Hellwig
2006-08-01 11:52   ` Nick Piggin
2006-08-01 14:54     ` Andrew Morton
2006-08-01 19:32   ` Andi Kleen

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=20060731123821.GC3658@stusta.de \
    --to=bunk@stusta.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reiser@namesys.com \
    --cc=vda.linux@googlemail.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