All of lore.kernel.org
 help / color / mirror / Atom feed
From: george anzinger <george@mvista.com>
To: Dave Jones <davej@codemonkey.org.uk>
Cc: Jeff Garzik <jgarzik@pobox.com>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: RFC: a code slush for 2.5?
Date: Mon, 03 Feb 2003 15:55:31 -0800	[thread overview]
Message-ID: <3E3F0173.2090206@mvista.com> (raw)
In-Reply-To: <20030203103146.GB31198@codemonkey.org.uk>

Dave Jones wrote:> On Mon, Feb 03, 2003 at 03:01:23AM -0500, Jeff 
Garzik wrote:
> 
>  > Linux 2.5 is a really exciting leap forward, in a lot a ways.  I'm still 
>  > hoping someone will draft a "What's new in 2.6?" document, just so we 
>  > have a nice _long_ list of all the improvements that have been made.
> 
> Feel free to munge http://www.codemonkey.org.uk/post-halloween-2.5.txt
> into whatever you were thinking of.  Or send me bits to add to it.
> 
> 		Dave
> 
Back before halloween Linus said that he only required the code to be 
in his in box by halloween and that he would continue to move stuff 
into the kernel post halloween, but would not accept any new features 
that were not already in his in box.

Has he ever said that he has finished the post halloween processing of 
these new features?

-- 
George Anzinger   george@mvista.com
High-res-timers:  http://sourceforge.net/projects/high-res-timers/
Preemption patch: http://www.kernel.org/pub/linux/kernel/people/rml


  reply	other threads:[~2003-02-03 23:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-03  8:01 RFC: a code slush for 2.5? Jeff Garzik
2003-02-03  8:05 ` Jeff Garzik
2003-02-03 10:31 ` Dave Jones
2003-02-03 23:55   ` george anzinger [this message]
2003-02-03 11:11 ` John Bradford
2003-02-03 18:18 ` Gerhard Mack
2003-02-04 12:32   ` Alan Cox

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=3E3F0173.2090206@mvista.com \
    --to=george@mvista.com \
    --cc=davej@codemonkey.org.uk \
    --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 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.