From: Andrew Morton <akpm@linux-foundation.org>
To: Eric Hopper <hopper@omnifarious.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Question about Reiser4
Date: Mon, 23 Apr 2007 10:40:42 -0700 [thread overview]
Message-ID: <20070423104042.87b50bb3.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070423135216.GA2744@omnifarious.org>
On Mon, 23 Apr 2007 06:52:16 -0700
Eric Hopper <hopper@omnifarious.org> wrote:
> On Mon, Apr 23, 2007 at 01:04:45AM -0700, Andrew Morton wrote:
> > The namesys engineers continue to maintain reiser4 and I continue to
> > receive patches for it.
> >
> > Right now I'd say that the main blockages for reiser4 are a) the developers
> > aren't presently asking for inclusion (afaik) and b) lack of reviewing
> > effort from other kernel developers.
>
> If someone else started asking for it to be included and responded to
> requests for the various code changes required to increase its quality
> to the required level, wouldn't that be enough? Basically, if someone
> forked it.
>
> Or does it specifically have to be namesys engineers?
That's not where the problem lies - the namesys guys are responsive and play
well with others. But they haven't received any "requests for the various code
changes" in over a year.
And I'm in the same boat as most everyone else: I haven't looked at the reiser4
code in ages. Right now I don't have anything like a list of outstanding
technical issues.
To get it unstuck we'd need a general push, get people looking at and testing
the code, get the vendors to have a serious think about it, etc. We could do
that - it'd require that the namesys people (and I) start making threatening
noises about merging it, I guess.
Or we could move all the reiser4 code into kernel/sched.c - that seems to get
people fired up.
next prev parent reply other threads:[~2007-04-23 17:40 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-23 2:00 Question about Reiser4 Eric Hopper
2007-04-23 2:31 ` Lee Revell
2007-04-23 3:56 ` Rik van Riel
2007-04-23 3:56 ` William Heimbigner
2007-04-23 5:47 ` Rik van Riel
2007-04-23 5:57 ` William Heimbigner
2007-04-23 6:07 ` Rik van Riel
2007-04-23 6:14 ` William Heimbigner
2007-04-23 6:20 ` Rik van Riel
2007-04-23 6:42 ` William Heimbigner
2007-04-23 8:04 ` Andrew Morton
2007-04-23 11:31 ` l.genoni
2007-04-23 13:52 ` Eric Hopper
2007-04-23 17:40 ` Andrew Morton [this message]
2007-04-23 18:36 ` Miguel Ojeda
2007-04-23 19:05 ` Andi Kleen
2007-04-23 22:56 ` Theodore Tso
2007-04-23 23:53 ` H. Peter Anvin
2007-04-24 0:14 ` Neil Brown
2007-04-24 0:21 ` H. Peter Anvin
2007-04-24 13:30 ` Jan Engelhardt
2007-04-24 0:19 ` Theodore Tso
2007-04-24 0:31 ` H. Peter Anvin
2007-04-24 1:17 ` Theodore Tso
2007-04-24 11:15 ` Denis Vlasenko
2007-04-25 6:39 ` Eric M. Hopper
2007-04-25 14:45 ` lkml777
2007-04-23 6:14 ` Jeff Chua
[not found] <20070423111939.c876c9cc.akpm@linux-foundation.org>
2007-04-24 14:43 ` Edward Shishkin
2007-04-24 19:39 ` Andi Kleen
2007-04-25 14:35 ` Edward Shishkin
2007-04-25 14:49 ` Jeff Chua
2007-04-25 15:06 ` lkml777
2007-04-25 15:50 ` Jeff Chua
2007-04-26 5:05 ` lkml777
2007-04-26 6:49 ` Jeff Chua
2007-04-26 5:09 ` lkml777
2007-04-26 6:48 ` Jeff Chua
2007-04-26 8:18 ` Jeff Chua
2007-04-27 7:16 ` lkml777
2007-04-26 0:44 ` lkml777
2007-04-25 0:12 ` lkml777
2007-04-25 6:26 ` Eric M. Hopper
2007-04-25 15:03 ` Edward Shishkin
2007-04-26 7:47 ` lkml777
2007-04-26 7:54 ` lkml777
2007-05-02 2:39 ` lkml777
2007-05-02 4:53 ` lkml777
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=20070423104042.87b50bb3.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=hopper@omnifarious.org \
--cc=linux-kernel@vger.kernel.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