From: fresco_pap@mail.ru
To: linux-fsdevel@vger.kernel.org
Subject: reiser4 merging
Date: Mon, 24 Apr 2006 16:53:58 +0400 [thread overview]
Message-ID: <910504635.20060424165358@mail.ru> (raw)
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.
next reply other threads:[~2006-04-24 12:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-24 12:53 fresco_pap [this message]
2006-04-24 16:22 ` reiser4 merging Bryan Henderson
-- strict thread matches above, loose matches on Subject: below --
2006-04-25 4:59 Peshehodov Andrey
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=910504635.20060424165358@mail.ru \
--to=fresco_pap@mail.ru \
--cc=linux-fsdevel@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