From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Sunil Naidu <akula2.shark@gmail.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
Chuck Ebbert <cebbert@redhat.com>,
Jesper Juhl <jesper.juhl@gmail.com>,
Chris Wright <chrisw@sous-sol.org>
Subject: Re: [Proposal] 2.6.18-stable release plans?
Date: Tue, 23 Jan 2007 18:41:30 +0100 [thread overview]
Message-ID: <45B648CA.3020507@s5r6.in-berlin.de> (raw)
In-Reply-To: <8355959a0701230538m2f1201b6u49853e65d4c69a57@mail.gmail.com>
Sunil Naidu wrote:
> I have to dig deep into the patch & kernel version to understand what
> are the features/implementations or fixes (patch). Problem here is 2
> ways:-
>
> 1) Identifying which is a better kernel (features) for
> Desktop/Embedded/Server (I know, info mentioned in Changelog. But
> still...)
>
> 2) Easily knowing which stable patch applies for which arch or sub
> system (better way)
>
> Proposal: Can maintainers implement this for better understanding of
> the Linux community (picking the best kernel or patch for the
> requirement) by adding a column on www.kernel.org home page?
...
This would be hard to organize and support. There are news sites like
LWN which give outlines of important kernel changes, and there are
mailinglists or community sites for architectures or driver subsystems
if you are interested in special platforms or drivers, and there is the
git repository metadata (via gitweb or directly from a locally cloned
git repo).
I for one am actually posting release notes to a users' mailinglist of
the drivers I'm interested in. But I can do this only because these are
drivers with very low rate of fixes or feature additions.
It's also not only a question of who writes such release notes, but also
of who the intended audience is. How fine-grained should the release
notes be?
Anyway --- if in doubt, your distributor's current kernel is the best one.
--
Stefan Richter
-=====-=-=== ---= =-===
http://arcgraph.de/sr/
next prev parent reply other threads:[~2007-01-23 17:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-22 22:13 2.6.18-stable release plans? Chuck Ebbert
2007-01-23 0:23 ` Jesper Juhl
2007-01-23 13:38 ` [Proposal] " Sunil Naidu
2007-01-23 17:41 ` Stefan Richter [this message]
2007-01-23 19:25 ` Sunil Naidu
2007-01-23 20:06 ` Stefan Richter
2007-01-23 20:33 ` Chuck Ebbert
2007-01-23 20:56 ` Adrian Bunk
2007-01-24 4:50 ` Daniel Barkalow
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=45B648CA.3020507@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=akula2.shark@gmail.com \
--cc=cebbert@redhat.com \
--cc=chrisw@sous-sol.org \
--cc=jesper.juhl@gmail.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.