public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nicholas Wourms <nwourms@netscape.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Abbott and Costello meet Crunch Time -- Penultimate 2.5 merge candidate list.
Date: Mon, 28 Oct 2002 07:15:38 -0500	[thread overview]
Message-ID: <apj9l9$8qm$1@main.gmane.org> (raw)
In-Reply-To: 3DBD1182.1000402@walrond.org

Andrew Walrond wrote:

> A concise and very useful summary of upcoming/potential features, not
> only for you kernel hackers but also for people using linux and trying
> to keep half an eye on whats brewing...
> I wish something like this was available all the time and not just in
> the run-up to a freeze

While not 100% accurate, kernelnewbies.org has done a very good job of 
tracking changes and pending changes during the 2.5 development life-cycle.  
I'm sure with another pair of eyes, they might be able to fully cover every 
potential development in a kernel's lifecycle.

*SIGH* This makes me nostalgic for Jim Pick's kernelnotes.org, a shame he 
didn't have time to maintain it anymore.

Cheers,
Nicholas



  parent reply	other threads:[~2002-10-28 12:08 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-28  2:17 Abbott and Costello meet Crunch Time -- Penultimate 2.5 merge candidate list Rob Landley
2002-10-28  8:25 ` Vamsi Krishna S .
2002-10-28  9:55   ` Skip Ford
2002-10-28 10:35     ` Vamsi Krishna S .
2002-10-28 10:29 ` Andrew Walrond
2002-10-28 10:40   ` Rob Landley
2002-10-28 12:15   ` Nicholas Wourms [this message]
2002-10-28 13:31   ` Dave Jones
2002-10-28 14:05     ` Andrew Walrond
2002-10-28 14:42       ` Andrew Walrond
2002-10-28 15:02       ` Alan Cox
2002-10-30  7:29 ` Dave Cinege
2002-10-30  7:40   ` Jeff Garzik
2002-10-30  8:22     ` Dave Cinege
2002-10-30  8:37       ` Russell King
2002-10-30  9:32         ` Dave Cinege
2002-10-30  8:41       ` Jeff Garzik
2002-10-30  8:51       ` Erik Andersen
2002-10-30  9:00         ` Miles Bader
2002-10-30  9:06           ` Jeff Garzik
2002-10-30  9:19             ` Miles Bader
2002-10-30  9:26               ` Jeff Garzik
2002-10-30  9:38                 ` Miles Bader
2002-10-30  9:42                   ` Erik Andersen
2002-10-30 10:50                   ` Jeff Garzik
2002-10-30  9:34             ` Russell King
2002-10-30 10:07               ` Dave Cinege
2002-10-30  9:36             ` Erik Andersen
2002-10-30 10:52               ` Jeff Garzik
2002-10-30  9:55           ` Dave Cinege
2002-10-30  9:59             ` Miles Bader
2002-10-30 10:24               ` Dave Cinege
2002-10-30 10:05             ` Jeff Garzik
2002-10-30 10:14               ` Dave Cinege
2002-10-30 10:24                 ` Jeff Garzik
2002-10-30 10:42                   ` Dave Cinege
2002-10-30 11:06                     ` Jeff Garzik
2002-10-30  9:55         ` Dave Cinege
2002-10-30 10:29           ` Jeff Garzik
2002-11-04  2:13           ` Rob Landley
2002-11-04  7:39             ` Help needed with IRQ on Ali chipset Jacek Pliszka
2002-11-04 13:10             ` Abbott and Costello meet Crunch Time -- Penultimate 2.5 merge candidate list Alan Cox
2002-11-04 22:52             ` Werner Almesberger
2002-11-04 23:02               ` Jeff Garzik
2002-11-04 18:16                 ` Rob Landley
2002-11-04 23:22                 ` Werner Almesberger
2002-10-30 14: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='apj9l9$8qm$1@main.gmane.org' \
    --to=nwourms@netscape.net \
    --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