From: "Sunil Naidu" <akula2.shark@gmail.com>
To: lkml <linux-kernel@vger.kernel.org>
Cc: "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 19:08:56 +0530 [thread overview]
Message-ID: <8355959a0701230538m2f1201b6u49853e65d4c69a57@mail.gmail.com> (raw)
In-Reply-To: <9a8748490701221623q1b61f03fva7b0ad7e7f30316f@mail.gmail.com>
On 1/23/07, Jesper Juhl <jesper.juhl@gmail.com> wrote:
>
> Now that 2.6.19 is out, most likely not. -stable releases are made
> for the latest stable 2.6.x kernel, once 2.6.x+1 is out that's the one
> -stable patches are made for (2.6.16 is an exception)..
Earlier I was going through the stable paches which apply for these
kernel version:
http://kernelnewbies.org/Linux_2_6_19
http://kernelnewbies.org/Linux_2_6_18
http://kernelnewbies.org/Linux_2_6_16
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?
Examples:
The latest stable version of the Linux kernel is: 2.6.19.2
*networking subsystem* 2007-01-10 19:11 UTC F V VI C Changelog
The latest prepatch for the stable Linux kernel tree is: 2.6.20-rc5
*x86 32/64* 2007-01-12 19:29 UTC B V VI C Changelog
> --
> Jesper Juhl <jesper.juhl@gmail.com>
Thanks,
Akula2
next prev parent reply other threads:[~2007-01-23 13:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-22 22:13 Chuck Ebbert
2007-01-23 0:23 ` Jesper Juhl
2007-01-23 13:38 ` Sunil Naidu [this message]
2007-01-23 17:41 ` [Proposal] " Stefan Richter
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=8355959a0701230538m2f1201b6u49853e65d4c69a57@mail.gmail.com \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®