public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@suse.de>
To: Rik van Riel <riel@conectiva.com.br>
Cc: Guillaume Boissiere <boissiere@adiglobal.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [STATUS 2.5]  July 17, 2002
Date: Wed, 17 Jul 2002 21:42:39 +0200	[thread overview]
Message-ID: <20020717214239.A32389@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.44L.0207171625140.12241-100000@imladris.surriel.com>

On Wed, Jul 17, 2002 at 04:25:56PM -0300, Rik van Riel wrote:
 > On Wed, 17 Jul 2002, Guillaume Boissiere wrote:
 > 
 > > New week, new status update...
 > > The details are at http://www.kernelnewbies.org/status/
 > >
 > > With the code freeze date approaching soon, it is obvious that many
 > > 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?
 > 
 > Please keep them as post-code freeze.  They might not go into
 > 2.5 and early 2.6, but that doesn't mean we should throw away
 > our TODO list ;)

Indeed. It may even be an idea to take what I started doing at
http://www.codemonkey.org.uk/Linux-2.5.html, merging the two
and Guillaume running with this if you have time, because these days,
between hacking and merging patches, I'm kept pretty busy, so updates
to that file are getting less frequent.

        Dave

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

  reply	other threads:[~2002-07-17 19:39 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
2002-07-17 19:25 ` Rik van Riel
2002-07-17 19:42   ` Dave Jones [this message]
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=20020717214239.A32389@suse.de \
    --to=davej@suse.de \
    --cc=boissiere@adiglobal.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@conectiva.com.br \
    /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