From: Christian Stroetmann <stroetmann@ontolinux.com>
To: doiggl@velocitynet.com.au,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux reiserfs-devel <reiserfs-devel@vger.kernel.org>
Subject: Re: Reiser4 status
Date: Fri, 30 Jul 2010 18:51:03 +0200 [thread overview]
Message-ID: <4C5302F7.2040102@ontolinux.com> (raw)
In-Reply-To: <a735d4d91548365914b3ad1550827187@mail.velocitynet.com.au>
Hi Glenn;
On the 30.07.2010 10:15, you wrote:
> On Fri, 31 Jul 2009 14:18:22 +0200, Edward Shishkin
> <edward.shishkin@gmail.com> wrote:
>
>> doiggl@velocitynet.com.au wrote:
>>
>>> Thanks Edward,
>>> How far away is Autumn or so for you ?
>>>
>> September - November.
>>
>>
>>> , as I don't know how far away that
>>> is, depends where you live :)
>>> Glenn
>>>
>>>
>>> On Fri, 31 Jul 2009 11:27:11 +0200, Edward Shishkin
>>> <edward.shishkin@gmail.com> wrote:
>>>
>>>
>>>> doiggl@velocitynet.com.au wrote:
>>>>
>>>>
>>>>> Hello
>>>>> Question: Is reiser4 scheduled to become part of the mainline kernel.
>>>>>
>>>>>
>>>>>
>>>> Yes, I think we'll start to explore
>>>> such opportunity in Autumn, or so..
>>>>
>>>> Edward.
>>>>
>>>>
>>>>
>>>>> I saw these:
>>>>> http://reiser4.wiki.kernel.org/index.php/Main_Page
>>>>> http://reiser4.wiki.kernel.org/index.php/TODO
>>>>> and it looks very promising, is that the latest info about reiser4
>>>>>
> and
>
>>>>> where its all up to ?
>>>>>
> Hello,
> I have two questions.
>
> - Is there any more news since Jul 2009 about progress of reiser4 becoming
> part of the mainline kernel ?
>
Yes, but actually not source code related. :-X
> - Have any of these items in this list been fixed ?
> http://marc.info/?l=reiserfs-devel&m=124069989217533&w=2
>
At first the one thingy and then the source code.
> Thanks Glenn
>
>
Revolution!!!
With all the best
Christian *<:o) O>-< -(D)>-<
parent reply other threads:[~2010-07-30 16:51 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <a735d4d91548365914b3ad1550827187@mail.velocitynet.com.au>]
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=4C5302F7.2040102@ontolinux.com \
--to=stroetmann@ontolinux.com \
--cc=doiggl@velocitynet.com.au \
--cc=linux-fsdevel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).