public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Landley <landley@trommello.org>
To: vda@port.imtp.ilyichevsk.odessa.ua, linux-kernel@vger.kernel.org
Cc: boissiere@nl.linux.org
Subject: Re: Crunch time -- Final merge candidates for 3.0 (the list).
Date: Sun, 20 Oct 2002 22:00:22 -0500	[thread overview]
Message-ID: <200210202200.22313.landley@trommello.org> (raw)
In-Reply-To: <200210210731.g9L7V8p21199@Port.imtp.ilyichevsk.odessa.ua>

On Monday 21 October 2002 07:23, Denis Vlasenko wrote:
> On 20 October 2002 21:49, Rob Landley wrote:
> > When Linus comes back, at best he's going to give a thumbs up or
> > thumbs down to each patch currently sitting there in front of him,
> > and then it's on to the feature freeze.  He may not take any of them,
> > or he may just take one or two.  But the best we can hope to do is
> > present him with a nice (short) list of tested patches. (Remember,
> > the less work Linus has to do, the higher the percentage of it that
> > will actually get done.)
>
> Well, maybe it makes sense to reduce flow of non-features patches
> for a couple of days to let Linus feel less buried in email?
> I think VM tweaking and such... It could be done after Linus
> say what got in and what did not.

It would also be nice to buy the dude his own private jet, but I'm not sure 
it's a practical suggestion in the short term. :)

Linus has already said he intends to read his mail with the "D" key when he 
gets back.  The point of collating the pending feature list is to pluck stuff 
out of the mess, shake it off a bit, and present him with a nice menu to make 
choices from on his return.

Deciding not to include stuff is Linus's perogative.  (More than that, it's 
more or less his JOB in kerneldom, acting as goalie for the main tree.)  Once 
again, we're just trying to make sure nothing gets dropped because he didn't 
see it rather than because he saw it and went "no".

In the past half-hour, the MMU-less patch and unlimited groups support have 
been fielded as "ready for 2.5", although I haven't seen URLs to either yet.  
Add Rusty's three items and we're up to... 19?  Plus Hans Reiser said reiser4 
will be ready around the 27th, so that's 20.

I don't think half that many will make it into 2.5, but some of them are 
small, so...

Oh, and of course one more little item that only Linus can merge (speaking of 
small, yet still important):

The version number: is it 2.6 or 3.0?

So that's 21. :)

Rob

      reply	other threads:[~2002-10-21  7:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-20 23:49 Crunch time -- Final merge candidates for 3.0 (the list) Rob Landley
2002-10-21  5:44 ` Hans Reiser
2002-10-21  6:03 ` Karim Yaghmour
2002-10-21  1:37   ` Rob Landley
2002-10-21  6:43     ` Andreas Dilger
2002-10-21  2:47       ` Rob Landley
2002-10-21  8:05         ` Andreas Dilger
2002-10-21  8:25         ` Andrew Morton
2002-10-21 11:56 ` Alan Cox
2002-10-21 12:23 ` Denis Vlasenko
2002-10-21  3:00   ` Rob Landley [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=200210202200.22313.landley@trommello.org \
    --to=landley@trommello.org \
    --cc=boissiere@nl.linux.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vda@port.imtp.ilyichevsk.odessa.ua \
    /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