From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Gerhard Mack <gmack@innerfire.net>
Cc: Jeff Garzik <jgarzik@pobox.com>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: RFC: a code slush for 2.5?
Date: 04 Feb 2003 12:32:04 +0000 [thread overview]
Message-ID: <1044361923.23312.28.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.44.0302031316040.4263-100000@innerfire.net>
On Mon, 2003-02-03 at 18:18, Gerhard Mack wrote:
> > So, if I had to make the proposal concrete, I would propose:
> > "code slush" effective immediately
> > code freeze, Easter holiday (April 19?)
> >
> > Comments/curses?
>
> It would be wise if a freeze was delayed until after at least IDE and
> console switching both work reliably with preempt enabled.
In which case April is unrealistic. Actually given the huge backlog
from Linus holiday its pointless to even try and guess at things right
now. We need to see what it looks like by about 2.5.63 to judge
Alan
prev parent reply other threads:[~2003-02-04 11:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-03 8:01 Jeff Garzik
2003-02-03 8:05 ` Jeff Garzik
2003-02-03 10:31 ` Dave Jones
2003-02-03 23:55 ` george anzinger
2003-02-03 11:11 ` John Bradford
2003-02-03 18:18 ` Gerhard Mack
2003-02-04 12:32 ` Alan Cox [this message]
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=1044361923.23312.28.camel@irongate.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=gmack@innerfire.net \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®