Matthew D. Fuller wrote:Unfortunately (for this developer-centric practice), the trend in large and/or important production environments is - as seen in Linux (and Solaris) - to severely limit major OS upgrades. Of course the existing possibility to do is excellent, but more and more end-users, especially big ones, are going with big Linux distributions that basically stay frozen (except for security upgrades) for years. And this idea gets a +1 from me - productions releases that are expected to run for years should be able to "just work" without upgrading to the "kernel of the week". To do this, a stable anchor-point is required and that's what -RELEASEes should be for. I think the fact that not all our -RELEASES are created equal (some are "extended support" releases) should be more advertised and explained.
| Len Brown | [PATCH 05/85] ACPI: Add "acpi.power_nocheck=1" to disable power state check in pow... |
| Andi Kleen | [PATCH] [2/50] x86_64: use core id bits for apicid_to_node initialization |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| Andrew Morton | 2.6.23-rc1-mm1 |
git: | |
| Gregory Haskins | [RFC PATCH 06/17] ioq: Add basic definitions for a shared-memory, lockless queue |
| Arjan van de Ven | Re: [GIT]: Networking |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| David Miller | Re: mac80211 truesize bugs |
