From: Diego Calleja <diegocg@gmail.com>
To: Theodore Tso <tytso@mit.edu>
Cc: Lexington.Luthor@gmail.com, linux-kernel@vger.kernel.org
Subject: "Why Reuser 4 still is not in" doc (was: 'reiserFS?')
Date: Sun, 16 Jul 2006 22:01:15 +0200 [thread overview]
Message-ID: <20060716220115.a1891231.diegocg@gmail.com> (raw)
In-Reply-To: <20060716174804.GA23114@thunk.org>
El Sun, 16 Jul 2006 13:48:04 -0400,
Theodore Tso <tytso@mit.edu> escribió:
> As far as I know not all of the problems were fixed. And it has been
> observed that given the abuse and accusations that were directed at
> the people who did decide to review it, that it would not at all
> surprising if some (all?) of reviewers may have decided they had
> better things to do. Getting things merged into mainline is not a
> right, and the reviewers are volunteers.....
Maybe it's too late and reiser 4 will get in in the next release, but
I've written this doc into the kernelnewbies' wiki:
http://wiki.kernelnewbies.org/WhyReiser4IsNotIn . If you disagree with
something in that doc, edit it or just answer to this mail what you want
to see in it and I'll add it myself.
next prev parent reply other threads:[~2006-07-16 20:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-16 16:16 reiserFS? Xavier Roche
2006-07-16 16:28 ` reiserFS? Christian Trefzer
2006-07-16 16:56 ` reiserFS? Theodore Tso
2006-07-16 17:26 ` reiserFS? Lexington Luthor
2006-07-16 17:48 ` reiserFS? Theodore Tso
2006-07-16 20:01 ` Diego Calleja [this message]
2006-07-16 21:11 ` "Why Reuser 4 still is not in" doc Lexington Luthor
2006-07-16 21:28 ` Joshua Hudson
2006-07-16 22:53 ` Lexington Luthor
2006-07-17 9:42 ` Jan Engelhardt
2006-07-17 16:38 ` Lexington Luthor
2006-07-20 6:52 ` Tilman Schmidt
2006-07-16 17:46 ` reiserFS? Dr. David Alan Gilbert
2006-07-16 18:14 ` reiserFS? Theodore Tso
2006-07-17 15:01 ` reiserFS? Matthias Andree
2006-07-17 21:07 ` reiserFS? Helge Hafting
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=20060716220115.a1891231.diegocg@gmail.com \
--to=diegocg@gmail.com \
--cc=Lexington.Luthor@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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