linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.x features log
Date: Fri, 7 Jan 2005 20:54:33 -0500	[thread overview]
Message-ID: <20050108015433.GC3210@redhat.com> (raw)
In-Reply-To: <41DEC82C.4040502@osdl.org>

On Fri, Jan 07, 2005 at 09:34:36AM -0800, Randy.Dunlap wrote:
 > 
 > I think that people really like the Dave Jones
 > 2.5/2.6 halloween information/update.  It contained a lot
 > of useful info in one place, with pointers to more details.
 > 
 > What I'm seeing (and getting a little concerned about,
 > although I dislike PR with a passion) is that the 2.6.x
 > continuous development cycle will cause us (the Linux
 > community) to miss logging some of these important new
 > features (outside of bk).  Has anyone kept a track of new
 > features that are being added in 2.6?
 > 
 > I'll keep a list (or someone else can -- DaveJ ?) if anyone
 > is interested in feeding items into it.  Or do distros
 > already keep such a running list of new features?

I don't really have the time right now to maintain it,
but if you want to take anything from the doc I wrote,
or push it for inclusion in the tree so others can
modify it at will, feel free.

		Dave


  parent reply	other threads:[~2005-01-08  1:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-07 17:34 2.6.x features log Randy.Dunlap
2005-01-07 18:46 ` jerome lacoste
2005-01-07 18:54 ` Rahul Karnik
2005-01-07 19:18 ` Diego Calleja
2005-01-08  1:54 ` Dave Jones [this message]
2005-01-09 12:18 ` Christoph Hellwig
2005-01-09 19:36   ` Dave Jones

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=20050108015433.GC3210@redhat.com \
    --to=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rddunlap@osdl.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;
as well as URLs for NNTP newsgroup(s).