From mboxrd@z Thu Jan 1 00:00:00 1970 From: fresco_pap@mail.ru Subject: reiser4 merging Date: Mon, 24 Apr 2006 16:53:58 +0400 Message-ID: <910504635.20060424165358@mail.ru> Reply-To: fresco_pap@mail.ru Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Return-path: Received: from mx27.mail.ru ([194.67.23.63]:5394 "EHLO mx27.mail.ru") by vger.kernel.org with ESMTP id S1750755AbWDXMyF (ORCPT ); Mon, 24 Apr 2006 08:54:05 -0400 Received: from [80.70.102.138] (port=14840 helo=adm) by mx27.mail.ru with asmtp id 1FY0Zm-000DaF-00 for linux-fsdevel@vger.kernel.org; Mon, 24 Apr 2006 16:54:03 +0400 To: linux-fsdevel@vger.kernel.org Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Hi all. I would like to ask some questions about reiser4 and its merging into mainline kernel. I has read discussions on KernelTrap, and I agree with most of arguments of Andrew Morton and company. But reiser4 is very flexible, high-performance and enough-stable filesystem, which must be immediately merged in vanilla kernel, i think. Could somebody answer me, which requirements should be satisfied by NameSys developers to merging reiser4 into mainline kernel? PS: sorry for my english -- I am from Russia... --- Andrey.