public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: James Simmons <jsimmons@transvirtual.com>
Cc: Tim Pepper <tpepper@vato.org>,
	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 03:21:12 +0300	[thread overview]
Message-ID: <3C476A78.6020500@namesys.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10201171458490.3503-100000@www.transvirtual.com>

James Simmons 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. 
>>>
>>I recall in June of 1999 Linus gave a kernel talk at BALUG and said he was
>>aiming for a year end release of 2.4 (but I think he meant that year ;) and
>>hoped to get the cycle down towards 6 months.  Is that type of timeline still
>>the target?
>>
>
>6 months. Never! I think we can do one year. I think this because for 2.5.X
>we see a bunch of projects working on different things for a long period
>of time. So it is just a matter of making everything work together. 
>
>   . ---
>   |o_o |
>   |:_/ |   Give Micro$oft the Bird!!!!
>  //   \ \  Use Linux!!!!
> (|     | )
> /'_   _/`\
> ___)=(___/
>
>
>
>
I think I basically  have no idea when 2.6 will ship and no idea when 
code freeze will hit, so I should work on the code and not worry until 
it is done.

Hans



  reply	other threads:[~2002-01-18  0:26 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 [this message]
2002-01-18  0:38     ` Alan Cox
2002-01-18 11:36       ` Hans Reiser
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=3C476A78.6020500@namesys.com \
    --to=reiser@namesys.com \
    --cc=boissiere@mediaone.net \
    --cc=jdomingo@internautas.org \
    --cc=jsimmons@transvirtual.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tpepper@vato.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