[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8355959a0701230538m2f1201b6u49853e65d4c69a57@mail.gmail.com>
Date: Tue, 23 Jan 2007 19:08:56 +0530
From: "Sunil Naidu" <akula2.shark@...il.com>
To: lkml <linux-kernel@...r.kernel.org>
Cc: "Chuck Ebbert" <cebbert@...hat.com>,
"Jesper Juhl" <jesper.juhl@...il.com>,
"Chris Wright" <chrisw@...s-sol.org>
Subject: Re: [Proposal] 2.6.18-stable release plans?
On 1/23/07, Jesper Juhl <jesper.juhl@...il.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@...il.com>
Thanks,
Akula2
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists