All of lore.kernel.org
 help / color / mirror / Atom feed
From: Edward Shishkin <edward.shishkin@gmail.com>
To: Christian Kujau <lists@nerdbynature.de>
Cc: reiserfs-devel@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: reiser4 for 2.6.33?
Date: Wed, 18 Nov 2009 14:50:17 +0100	[thread overview]
Message-ID: <4B03FB99.6070705@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.01.0911171420480.27639@bogon.housecafe.de>

As I told already for reiser4 inclusion we need the following:

(a) plugin design document;
(b) full description of what is going on in respond to memory
    pressure notifications;

The (a) is not yet ready and I don't have a time to explain
personally to everyone why the plugin stuff is not crappy. It will
be posted in a magazine with proper background, because all
Namesys projects traditionally have academic sources. So wait...

Actually there is no hurry. Taking into account common situation
with file systems, I am not afraid that reiser4 will get obsolete.

Thanks,
Edward.

Christian Kujau wrote:
> It's autumn[0] already and even with 2.6.32 not quite ready yet, let me 
> be the one asking the inevitable question:
>  What are the plans for reiser4 being included in 2.6.33? The 
> diffstat for the 2.6.31 patch looks rather promising, at least to me:
>
> $ diffstat reiser4-for-2.6.31.patch | grep -v fs/reiser4
>  Documentation/Changes                         |   12 
>  Documentation/filesystems/reiser4.txt         |   75 
>  fs/Kconfig                                    |    1 
>  fs/Makefile                                   |    1 
>  fs/fs-writeback.c                             |    5 
>  include/linux/fs.h                            |    3 
>  include/linux/mm.h                            |    1 
>  mm/filemap.c                                  |    3 
>  mm/page-writeback.c                           |   26 
>  170 files changed, 77581 insertions(+), 1 deletion(-)
>
> Or maybe it can find a place in -staging if there are still strong 
> objections against a general inclusion?
>
> Thanks,
> Christian.
>
> [0] http://marc.info/?l=reiserfs-devel&m=124904274311847&w=2
>   


  reply	other threads:[~2009-11-18 13:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-17 22:29 reiser4 for 2.6.33? Christian Kujau
2009-11-18 13:50 ` Edward Shishkin [this message]
2009-11-18 19:12   ` Christian Kujau
2009-12-03  1:22   ` drwowe

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=4B03FB99.6070705@gmail.com \
    --to=edward.shishkin@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lists@nerdbynature.de \
    --cc=reiserfs-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.