From: Dave Jones <davej@suse.de>
To: Daniel Phillips <phillips@arcor.de>
Cc: Rik van Riel <riel@conectiva.com.br>,
Andrew Morton <akpm@zip.com.au>,
Linus Torvalds <torvalds@transmeta.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [patch 1/13] minimal rmap
Date: Wed, 17 Jul 2002 22:50:06 +0200 [thread overview]
Message-ID: <20020717225006.C9489@suse.de> (raw)
In-Reply-To: <E17UvXF-0004Pu-00@starship>
On Wed, Jul 17, 2002 at 10:36:33PM +0200, Daniel Phillips wrote:
> > Code _freeze_ that is, duh.
> Is the halloween freeze a code freeze? I thought it was a feature freeze.
Your thinking is correct. No new features after halloween, but
obviously code *fixing* those that made it before the cut-off
will still be taken right up to 2.6.0
I have visions of pre-freeze October as everyone goes mad rushing
to get their last minute features in, and then post-freeze November
the endless. "No really, it's just a fix!" mails.
Fun times lie ahead.
Dave
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
next prev parent reply other threads:[~2002-07-17 20:47 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-17 5:29 [patch 1/13] minimal rmap Andrew Morton
2002-07-17 8:24 ` Russell King
2002-07-17 12:10 ` Rik van Riel
2002-07-17 12:21 ` Rik van Riel
2002-07-17 17:57 ` Daniel Phillips
2002-07-17 18:11 ` Robert Love
2002-07-17 18:26 ` Daniel Phillips
2002-07-17 20:37 ` Rik van Riel
2002-07-17 20:42 ` Robert Love
2002-07-17 20:46 ` Daniel Phillips
2002-07-17 20:48 ` Robert Love
2002-07-17 19:31 ` Rik van Riel
2002-07-17 19:38 ` Daniel Phillips
2002-07-17 19:41 ` Rik van Riel
2002-07-17 19:55 ` Daniel Phillips
2002-07-17 20:04 ` Rik van Riel
2002-07-17 20:13 ` Daniel Phillips
2002-07-17 20:25 ` Rik van Riel
2002-07-17 20:25 ` Rik van Riel
2002-07-17 20:36 ` Daniel Phillips
2002-07-17 20:39 ` Rik van Riel
2002-07-17 20:50 ` Dave Jones [this message]
2002-07-17 20:53 ` Robert Love
2002-07-22 2:40 ` Andrew Morton
2002-07-17 19:42 ` Robert Love
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=20020717225006.C9489@suse.de \
--to=davej@suse.de \
--cc=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=phillips@arcor.de \
--cc=riel@conectiva.com.br \
--cc=torvalds@transmeta.com \
/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