From: Ralph Ulrich <eulenreich@gmx.de>
To: reiserfs-devel@vger.kernel.org
Subject: Re: The reiser4 .... what it really means
Date: Thu, 11 Dec 2008 12:35:42 +0100 [thread overview]
Message-ID: <4940FB0E.8050102@gmx.de> (raw)
In-Reply-To: <494062F6.2040809@gmx.de>
What this really means is:
They forked reiser4 with brtfs to handly more and more data.
But the fortunate way is to fork the kernel to fit him right to reiser4.
The aim should be to connect the data better and better, to go
aiming little gadgets introducing with some real artificial intelligence.
That is the vision of reiser4!
Ralph
next prev parent reply other threads:[~2008-12-11 11:35 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-10 21:34 The reiser4 programming style is recursive? Ralph Ulrich
2008-12-10 21:41 ` Teran McKinney
2008-12-10 22:07 ` Ralph Ulrich
2008-12-10 22:21 ` David Backeberg
2008-12-11 0:09 ` Ralph Ulrich
2008-12-11 4:49 ` Toby Thain
2008-12-10 22:23 ` Edward Shishkin
2008-12-11 0:23 ` Ralph Ulrich
2008-12-11 16:57 ` Edward Shishkin
2008-12-11 17:37 ` Ralph Ulrich
2008-12-11 18:12 ` Edward Shishkin
2008-12-11 19:05 ` Ralph
2008-12-11 22:56 ` Edward Shishkin
2008-12-12 16:21 ` Ralph
2008-12-13 19:30 ` Edward Shishkin
2008-12-14 15:24 ` The... reiser4 with no ambiguity Ralph Ulrich
2008-12-14 19:17 ` Edward Shishkin
2008-12-16 0:59 ` Ralph Ulrich
2008-12-17 21:49 ` Edward Shishkin
2008-12-18 12:28 ` Ralph Ulrich
2008-12-21 13:38 ` Edward Shishkin
2008-12-11 0:46 ` The reiser4 .... why it is the future Ralph Ulrich
2008-12-11 11:35 ` Ralph Ulrich [this message]
2008-12-11 12:22 ` The reiser4 .... what it really means Ralph Ulrich
2008-12-11 14:36 ` Alexander Lyamin
2008-12-11 17:11 ` The reiser4 ....SDK for experiments outside kernel Ralph
2008-12-11 19:10 ` Edward Shishkin
2008-12-11 19:56 ` Ralph
2008-12-11 23:03 ` Edward Shishkin
2008-12-11 23:04 ` Christian Stroetmann OntoLab
2008-12-12 0:54 ` Ralph
2008-12-11 14:56 ` The reiser4 .... what it really means Christian Stroetmann OntoLab
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=4940FB0E.8050102@gmx.de \
--to=eulenreich@gmx.de \
--cc=reiserfs-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.