From: Edward Shishkin <edward.shishkin@gmail.com>
To: doiggl@velocitynet.com.au
Cc: reiserfs-devel@vger.kernel.org
Subject: Re: Reiser4 status
Date: Fri, 31 Jul 2009 11:27:11 +0200	[thread overview]
Message-ID: <4A72B8EF.1020301@gmail.com> (raw)
In-Reply-To: <8e5d545b16c5a0edc77774bf4b2e2d2f@mail.velocitynet.com.au>
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 ?
next prev parent reply	other threads:[~2009-07-31  9:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-31  4:32 Reiser4 status doiggl
2009-07-31  9:27 ` Edward Shishkin [this message]
2009-07-31 10:47   ` doiggl
2009-07-31 12:18     ` Edward Shishkin
2010-07-30  8:15       ` doiggl
2010-07-30 12:40         ` Edward Shishkin
2010-07-30 16:51         ` Christian Stroetmann
2009-07-31  9:38 ` Rick
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=4A72B8EF.1020301@gmail.com \
    --to=edward.shishkin@gmail.com \
    --cc=doiggl@velocitynet.com.au \
    --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).