From: Edward Shishkin <edward@namesys.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"Vladimir V. Saveliev" <vs@namesys.com>,
Alex Zarochentsev <zam@namesys.com>,
Linux kernel mailing list <linux-kernel@vger.kernel.org>,
Eric Hopper <hopper@omnifarious.org>, Lex Lyamin <flx@msu.ru>,
William Heimbigner <icxcnika@mar.tar.cc>,
Rik van Riel <riel@redhat.com>, Xu CanHao <xucanhao@gmail.com>
Subject: Re: Question about Reiser4
Date: Wed, 25 Apr 2007 18:35:03 +0400 [thread overview]
Message-ID: <462F6717.70508@namesys.com> (raw)
In-Reply-To: <20070424193921.GA17129@one.firstfloor.org>
Andi Kleen wrote:
>>Because there are unaddressed items in this todo list:
>>http://pub.namesys.com/Reiser4/ToDo
>>The main issues here are xattrs and support for blocksize != pagesize.
>>
>>
>
>I would consider both to be optional. We have various file systems
>in tree that don't support either (e.g. JFS only supports 4K blocks
>and OCFS2 doesn't support xattr) They shouldn't block merging.
>
>
>
xattrs also were considered as some guarantee of vendor support.
If possible, then we'll address it as low-priority issue.
Maybe somebody will help.. (xattrs support should go as incremental
update of FPL-subversion for reiser4 kernel module and reiser4progs).
>>2. Who will maintain this?
>>
>>Currently there are two namesys employees working mostly on
>>enthusiasm. Divide them into 2 file systems, plus many people who
>>really help with fixing problems.
>>
>>
>
>Merging will probably be a peak of work for the necessary changes,
>then hopefully the work will be less once you're in tree because
>you don't need to track mainline anymore
>(assuming not to many bugs come in from users)
>
>-Andi
>
>
Hope we survive this, at least such peaks is not something new in
our practice.
Well, gentlemen, so we'll address other items (except #26, 27) and
resume this discussion.
Thanks,
Edward.
next prev parent reply other threads:[~2007-04-25 14:35 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070423111939.c876c9cc.akpm@linux-foundation.org>
2007-04-24 14:43 ` Question about Reiser4 Edward Shishkin
2007-04-24 19:39 ` Andi Kleen
2007-04-25 14:35 ` Edward Shishkin [this message]
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
[not found] ` <b6a2187b0704270937g18f305cdxfdd54349fb73f3ea@mail.gmail.com>
2007-04-27 23:38 ` Question about Reiser4 (how to boot it?) lkml777
2007-04-28 1:40 ` Jeff Chua
2007-05-02 5:00 ` lkml777
2007-04-28 18:29 ` Andi Kleen
2007-05-02 2:45 ` lkml777
2007-04-26 0:44 ` Question about Reiser4 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
2007-04-23 2:00 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
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
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=462F6717.70508@namesys.com \
--to=edward@namesys.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=flx@msu.ru \
--cc=hopper@omnifarious.org \
--cc=icxcnika@mar.tar.cc \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@redhat.com \
--cc=vs@namesys.com \
--cc=xucanhao@gmail.com \
--cc=zam@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