From: Dave Jones <davej@redhat.com>
To: Christoph Hellwig <hch@infradead.org>,
"Randy.Dunlap" <rddunlap@osdl.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.x features log
Date: Sun, 9 Jan 2005 14:36:43 -0500 [thread overview]
Message-ID: <20050109193642.GB5528@redhat.com> (raw)
In-Reply-To: <20050109121830.GA25170@infradead.org>
On Sun, Jan 09, 2005 at 12:18:30PM +0000, Christoph Hellwig wrote:
> 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?
>
> Debian actually patches Dave's post_halloween document into
> Documentation. Maybe we should put it there for mainline
> aswell and make sure to update it when doing major changes?
I've said "Sure, go for it" to a number of people who
brought this up, but nothing has ever come of it.
I'll send it to Linus myself later today. 8)
Dave
prev parent reply other threads:[~2005-01-09 19:37 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
2005-01-09 12:18 ` Christoph Hellwig
2005-01-09 19:36 ` Dave Jones [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=20050109193642.GB5528@redhat.com \
--to=davej@redhat.com \
--cc=hch@infradead.org \
--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 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.