From: Hans Reiser <reiser@namesys.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Jose Luis Domingo Lopez <jdomingo@internautas.org>,
Guillaume Boissiere <boissiere@mediaone.net>,
linux-kernel@vger.kernel.org
Subject: Re: [STATUS 2.5] January 17, 2001
Date: Fri, 18 Jan 2002 14:36:10 +0300 [thread overview]
Message-ID: <3C4808AA.3010805@namesys.com> (raw)
In-Reply-To: <E16RN2p-0005VC-00@the-village.bc.nu>
Alan Cox wrote:
>>Have you heard anything about when Linus intends to code freeze? In my
>>planning I am assuming Sept. 30 is way earlier than 2.6 would ship. I
>>remember how long 2.4 took, and I simply assume 2.6 will be the same.
>> At any rate, there is no way we'll be done earlier than September: it
>>is a deep rewrite. Code looks so much better than the old code...., but
>>it is completely new code.
>>
>
>If Linus says september freezes in september and ships for christmas I will
>be most suprised. If he says september freezes the may after and ships the
>december after that I'd count it normal
>
>Personally I'd really like to see the block I/O stuff straightened out. The
>neccessary VM bits done, device driver updates and a September freeze. I
>think it can be done, and I think the resulting kernel will be way way
>better for people with 1Gb+ of RAM, so much better that its worth making a
>clear release at that point.
>
>Alan
>
>
Let us encourage him to give us some warning, like 60 days of warning.
Let us also encourage him to code freeze VM and VFS first not last (I
think he agrees with this fortunately). I am not going to say anything
about when I would like that freeze to hit, except that we won't be
ready before September/October because I am finally able to take the
time to do things right in the design and so I will. If he freezes in
~September, we'll have an experimental Reiser4 for him. Or so I fondly
hope and vaporize.;-)
What about the zero-copy stuff I keep hearing rumors about? How ready
to go is it? We want ReiserFS to be well-integrated with it if possible.
Hans
next prev parent reply other threads:[~2002-01-18 11:40 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-17 7:13 [STATUS 2.5] January 17, 2001 Guillaume Boissiere
2002-01-17 9:09 ` Stefan Smietanowski
2002-01-17 10:03 ` Russell King
2002-01-17 11:21 ` Dave Jones
2002-01-17 12:40 ` Erik Mouw
2002-01-17 21:47 ` Jose Luis Domingo Lopez
2002-01-17 22:14 ` Tim Pepper
2002-01-17 22:21 ` Hans Reiser
2002-01-17 22:39 ` Tim Pepper
2002-01-17 23:02 ` James Simmons
2002-01-18 0:21 ` Hans Reiser
2002-01-18 0:38 ` Alan Cox
2002-01-18 11:36 ` Hans Reiser [this message]
2002-01-17 22:22 ` Guillaume Boissiere
2002-01-17 22:30 ` Tim Pepper
2002-01-20 1:02 ` H. Peter Anvin
2002-01-18 4:47 ` Guillaume Boissiere
2002-01-18 0:23 ` Anton Altaparmakov
2002-01-18 0:50 ` Chris Chabot
2002-01-18 4:35 ` Guillaume Boissiere
2002-01-18 2:02 ` Arnaldo Carvalho de Melo
2002-01-21 12:39 ` Pavel Machek
2002-01-24 17:40 ` James Simmons
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=3C4808AA.3010805@namesys.com \
--to=reiser@namesys.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=boissiere@mediaone.net \
--cc=jdomingo@internautas.org \
--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