From: Dave Jones <davej@suse.de>
To: Patrick Mochel <mochel@osdl.org>
Cc: "Randy.Dunlap" <rddunlap@osdl.org>,
Guillaume Boissiere <boissiere@adiglobal.com>,
linux-kernel@vger.kernel.org
Subject: Re: [STATUS 2.5] July 17, 2002
Date: Wed, 17 Jul 2002 21:19:07 +0200 [thread overview]
Message-ID: <20020717211907.H18170@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0207170916360.2542-100000@cherise.pdx.osdl.net>
On Wed, Jul 17, 2002 at 09:19:39AM -0700, Patrick Mochel wrote:
> > | With the code freeze date approaching soon, it is obvious that many
> > Oct. 31 is feature freeze date, or so several of us understood.
>
> That is correct. And, for a feature, we only need a header file to be in,
> right? ;)
Hmmmmmm 8-)
wrt to post-halloween features, things like new drivers that require no
core changes aren't an issue, but things like ripping out the VM and
replacing with a new one should probably wait until 2.6.10 or so.[*]
> Please don't. While it would be nice if x86 init were a bit nicer, and
> things like CPUs were added in a 'hotpluggable' manner, I won't be
> dedicating time to this. At least not in near future...
Rusty seems to have a good handle on the hotplug bits, whether
bringing them up in a hotplug manner is his intention I'm not sure,
but it does seem to be going in that direction afaics.
Dave
[*] j/k of course. (at least, I hope so).
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
next prev parent reply other threads:[~2002-07-17 19:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-17 5:24 [STATUS 2.5] July 17, 2002 Guillaume Boissiere
2002-07-17 16:10 ` Randy.Dunlap
2002-07-17 16:19 ` Dave Jones
2002-07-17 16:19 ` Patrick Mochel
2002-07-17 19:19 ` Dave Jones [this message]
2002-07-17 19:25 ` Rik van Riel
2002-07-17 19:42 ` Dave Jones
2002-07-18 4:30 ` Guillaume Boissiere
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=20020717211907.H18170@suse.de \
--to=davej@suse.de \
--cc=boissiere@adiglobal.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.org \
--cc=rddunlap@osdl.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