From: Alexander Zarochentsev <zam@namesys.com>
To: reiserfs-list@namesys.com
Cc: "Vladimir V. Saveliev" <vs@namesys.com>,
reiserfs-dev <reiserfs-dev@namesys.com>
Subject: Re: reiser4 for 2.6.16 (version 3)
Date: Tue, 30 May 2006 15:54:35 +0400 [thread overview]
Message-ID: <200605301554.35901.zam@namesys.com> (raw)
In-Reply-To: <1148923857.6482.12.camel@tribesman.namesys.com>
On Monday 29 May 2006 21:30, Vladimir V. Saveliev wrote:
> Hello
>
> ftp://ftp.namesys.com/pub/reiser4-for-2.6/2.6.16/reiser4-for-2.6.16-3
>.patch.gz contains the most recent reiser4 code which is considered
> stable inside Namesys. This code is supposed to be in mm kernel next
> to 2.6.17-rc4-mm3.
>
> Please try it. Any feedback is welcome.
it works on the Cuba server.
uptime is
3:54pm up 5:25, 2 users, load average: 0,00, 0,00, 0,00
>
>
--
Alex.
next prev parent reply other threads:[~2006-05-30 11:54 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-29 17:30 reiser4 for 2.6.16 (version 3) Vladimir V. Saveliev
2006-05-30 11:54 ` Alexander Zarochentsev [this message]
2006-05-30 13:49 ` mail
2006-05-30 15:31 ` Vladimir V. Saveliev
2006-05-31 8:54 ` mail
2006-06-01 5:19 ` Hans Reiser
2006-06-01 8:18 ` Vladimir V. Saveliev
2006-05-31 15:54 ` Sergey Ivanov
2006-05-31 16:30 ` Vladimir V. Saveliev
2006-05-31 18:24 ` Sergey Ivanov
2006-05-30 15:59 ` Marcus Furlong
2006-05-30 16:38 ` mail
2006-05-30 18:08 ` Alexey Polyakov
2006-05-31 16:40 ` Francesco Biscani
2006-05-31 23:59 ` rvalles
[not found] ` <20060531235811.GA11674@rvalles.homedns.org.>
2006-06-06 2:04 ` rvalles
[not found] ` <20060606020422.GB32109@rvalles.homedns.org.>
2006-06-06 5:31 ` reiser4 for 2.6.16 (version 3) (or what is in the reiser4 todo list) Hans Reiser
2006-06-06 19:26 ` [BUG] reiser4 for 2.6.16 (version 4) Francesco Biscani
2006-06-06 19:34 ` zam, can you look at this? Hans Reiser
2006-06-09 17:23 ` Alexander Zarochentsev
-- strict thread matches above, loose matches on Subject: below --
2006-06-05 23:15 reiser4 for 2.6.16 (version 3) Frieder Bürzele
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=200605301554.35901.zam@namesys.com \
--to=zam@namesys.com \
--cc=reiserfs-dev@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=vs@namesys.com \
/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.