From mboxrd@z Thu Jan 1 00:00:00 1970 From: Edward Shishkin Subject: Re: reiser4 for 2.6.33? Date: Wed, 18 Nov 2009 14:50:17 +0100 Message-ID: <4B03FB99.6070705@gmail.com> References: Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: reiserfs-devel-owner@vger.kernel.org List-ID: Content-Type: text/plain; charset="us-ascii"; format="flowed" To: Christian Kujau Cc: reiserfs-devel@vger.kernel.org, LKML 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 >