From: Adrian Bunk <bunk@stusta.de>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: 2.6.16.x will be a long-living kernel series
Date: Mon, 20 Mar 2006 13:02:29 +0100 [thread overview]
Message-ID: <20060320120229.GB22317@stusta.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0603192216450.3622@g5.osdl.org>
As proposed some time ago [1], I'll continue the 2.6.16.x series after
2.6.17 will be released.
A short FAQ is below.
cu
Adrian
[1] http://lkml.org/lkml/2005/12/3/55
Q:
What will be the rules for patch inclusion in the 2.6.16.x series?
A:
There will be more relaxed rules similar to the rules in kernel 2.4
after the release of kernel 2.6.0 (e.g. driver updates will be allowed).
Q:
Why not start with the more relaxed rules before the release of 2.6.17?
A:
After 2.6.16.y following the usual stable rules, the kernel should be
relatively stable and well-tested giving the best possible basis for a
long-living series.
Q:
How long will this 2.6.16 series be maintained?
A:
That depends on how long people use it and contribute patches.
Q:
Stable API/ABI for external modules?
A:
No.
next prev parent reply other threads:[~2006-03-20 12:02 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-20 6:23 Linux v2.6.16 Linus Torvalds
2006-03-20 12:02 ` Adrian Bunk [this message]
2006-03-20 12:05 ` 2.6.16.x will be a long-living kernel series Arjan van de Ven
2006-03-20 12:12 ` Adrian Bunk
2006-03-20 13:03 ` Arjan van de Ven
2006-03-24 0:22 ` Adrian Bunk
2006-03-20 19:22 ` Jan Engelhardt
2006-03-20 17:19 ` Linux v2.6.16 Joe Korty
2006-03-20 19:04 ` Jeff Garzik
2006-03-20 19:25 ` Jan Engelhardt
2006-03-20 19:32 ` Joe Korty
2006-03-20 19:33 ` Linus Torvalds
2006-03-20 21:05 ` Andreas Schwab
2006-03-20 22:52 ` Matthias Andree
2006-03-22 5:22 ` Peter Williams
2006-03-22 6:31 ` Ashok Raj
2006-03-22 13:08 ` Ashok Raj
2006-03-22 13:25 ` Michal Piotrowski
2006-03-22 17:39 ` Rafael J. Wysocki
2006-03-22 17:54 ` Ashok Raj
2006-03-22 18:11 ` Rafael J. Wysocki
2006-03-22 18:27 ` Ashok Raj
2006-03-22 20:40 ` Rafael J. Wysocki
2006-03-22 21:00 ` Ashok Raj
2006-03-22 21:36 ` Rafael J. Wysocki
2006-03-22 22:27 ` Peter Williams
2006-03-28 16:39 ` Linux v2.6.16(.1) - compile failure Athanasius
2006-03-31 17:09 ` 'make oldconfig' sub-optimal 2.6.15 -> 2.6.16(.1) (was Re: Linux v2.6.16(.1) - compile failure) Athanasius
2006-04-01 9:18 ` netfilter: IP_NF_CONNTRACK_NETLINK=y, IP_NF_NAT=m compile error Adrian Bunk
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=20060320120229.GB22317@stusta.de \
--to=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox