From: Marc Perkel <marc@perkel.com>
To: linux-kernel@vger.kernel.org
Subject: Reiser 4 - the BIG picture - (think BIG picture)
Date: Mon, 19 Sep 2005 08:45:27 -0700 [thread overview]
Message-ID: <432EDD17.3080107@perkel.com> (raw)
OK - lets reset on the personal attacks stuff. I know there are people
who like to goat people into fighting about this but STOP IT.
The question that should be answered is - is Reiser4 ready yet - and
that should be answered only by people who actually know what they are
talking about. Someone saying "I had Reiser 3 in 2001 and it crashed my
drive man" has nothing to do with this decision.
So - may I ask ....
Does Reiser 4 break anything? What is the down side of including it?
Does Reiser 4 lack anything that is required? Has it met the criteria
for inclusion?
If Reiser 4 isn't ready then what specifically needs to be done to get
it ready? Let's post a list.
How ready is Reiser 4 compared to other file systems at the point of
inclusion? Is it ripe yet?
next reply other threads:[~2005-09-19 15:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-19 15:45 Marc Perkel [this message]
2005-09-19 16:00 ` Reiser 4 - the BIG picture - (think BIG picture) Randy.Dunlap
2005-09-19 16:11 ` Maciej Soltysiak
2005-09-19 16:16 ` Randy.Dunlap
2005-09-19 16:24 ` Maciej Soltysiak
2005-09-19 16:19 ` Kyle Moffett
2005-09-19 17:50 ` Marc Perkel
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=432EDD17.3080107@perkel.com \
--to=marc@perkel.com \
--cc=linux-kernel@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