All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@suse.de>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: Guillaume Boissiere <boissiere@adiglobal.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [STATUS 2.5]  July 17, 2002
Date: Wed, 17 Jul 2002 18:19:02 +0200	[thread overview]
Message-ID: <20020717181901.G18170@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.33L2.0207170908060.29653-100000@dragon.pdx.osdl.net>

On Wed, Jul 17, 2002 at 09:10:19AM -0700, Randy.Dunlap 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.

yep.

 > | of these projects will not get merged in the next 3 months.
 > | What would you rather me do?  Keep them in here just for reference,
 > | mark them as post-code freeze or just delete them?
 > I think that you have more than 3 months to continue updating this.  :)

It would actually be useful to have some more people propose input
on Guillaume's list at some point, or even to suggest removal of
items unlikely to happen.

 > | o Started     Reorder x86 initialization                      (Dave Jones,
 > | Randy Dunlap)
 > Please change this one to Pat Mochel.

There's also a lot of cross-over with this item and the
x86 subarch support which James Bottomley has been working on.
I've been kicking that patch around a little the last few days,
and I'll be merging it soon, so we can get a taste for how
arch/i386/ *could* look.

        Dave

-- 
| Dave Jones.        http://www.codemonkey.org.uk
| SuSE Labs

  reply	other threads:[~2002-07-17 16: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 [this message]
2002-07-17 16:19   ` Patrick Mochel
2002-07-17 19:19     ` Dave Jones
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=20020717181901.G18170@suse.de \
    --to=davej@suse.de \
    --cc=boissiere@adiglobal.com \
    --cc=linux-kernel@vger.kernel.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 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.