From: "Nicholas S. Wourms" <nwourms@netscape.net>
To: Hans Reiser <reiser@namesys.com>
Cc: reiserfs-list@namesys.com
Subject: Re: Reiser4's status of this week.
Date: Sat, 19 Jun 2004 14:15:39 -0400 [thread overview]
Message-ID: <40D482CB.1080303@netscape.net> (raw)
In-Reply-To: <40D45B6C.7000002@namesys.com>
Hans Reiser wrote:
> stone_wang@sohu.com wrote:
>
>> Hi,Hans:
>>
>> Your website are saying "Reiser4 is in final testing, and will ship
>> soon!" It has been saying that for a long time :(
>>
>>
>> When could Reiser4 be finaly released? We are eager to try it.
>>
>> Regards.
>>
>> Stone.
>>
>>
>>
>>
> next week. or so we hope.
Hans,
I've noticed that there seems to be a problem with your
reiser4-linux-2.6 bitkeeper repository. Unlike the 2.5 version I used
awhile back, this one seems to just be an old copy of the stock
linux-2.6.5 kernel with the 2.6.5-mm2 patches added. None of the
reiser4 base or extra patches seem to have been added (excluding the
ones for fs/reiser4). Would someone mind fixing this? Don't you have
an internal repository with all the modifications in the base and extra
series applied? If your internal tree can't be exported, can you
provide a snapshot BK-style(not gnu) patch against linus-current?
I've also noticed, as has been noted in the past, that bk pulls are
still broken. Someone mentioned that it is a problem with the new bk.
If this is true, why not contact Larry for support? Not that it matters
now, since the reiser4-linux-2.6 isn't usable, but it might be helpful
for future syncs.
Cheers,
Nicholas
next prev parent reply other threads:[~2004-06-19 18:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-19 13:19 Reiser4's status of this week stone_wang
2004-06-19 15:27 ` Hans Reiser
2004-06-19 16:15 ` Reiser4 on x86_64 Claudio Martins
2004-06-19 18:15 ` Nicholas S. Wourms [this message]
2004-06-19 22:08 ` Reiser4's status of this week mjt
2004-06-19 22:51 ` Hans Reiser
2004-06-19 23:27 ` Nicholas S. Wourms
2004-06-19 22:49 ` Hans Reiser
2004-06-19 23:42 ` Nicholas S. Wourms
2004-06-20 12:24 ` Alex Zarochentsev
2004-06-21 20:26 ` Nicholas S. Wourms
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=40D482CB.1080303@netscape.net \
--to=nwourms@netscape.net \
--cc=reiser@namesys.com \
--cc=reiserfs-list@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.