From: Maciej Soltysiak <solt2@dns.toxicfilms.tv>
To: linux-kernel@vger.kernel.org
Subject: Re: What's Happening with Reiser 4?
Date: Thu, 5 Jan 2006 23:59:59 +0100 [thread overview]
Message-ID: <807369901.20060105235959@dns.toxicfilms.tv> (raw)
In-Reply-To: <43BD7A26.6040207@perkel.com>
Hi,
> I haven't heard any Reiser4 news lately. What's happening with that?
> Will it ever be merged?
I am not the r4 spokesman but I can say what I recorded lately.
I think r4 folks are still working on Christoph's suggestions that include
changes required for the code to be merged.
Some of those changes made the code unstable a bit and those issues were
and some still are being adressed I think.
The r4 mailing list is kind of silent lately but there were a few important
"fixed now" reports from a couple of users.
Maybe someone from namesys could elaborate on their short-term plans.
Best regards,
Maciej Soltysiak
prev parent reply other threads:[~2006-01-05 23:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-05 19:57 Marc Perkel
2006-01-05 22:59 ` Maciej Soltysiak [this message]
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=807369901.20060105235959@dns.toxicfilms.tv \
--to=solt2@dns.toxicfilms.tv \
--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
all inboxes | Powered by JetHome®