From: "Jörg-Volker Peetz" <jvpeetz@web.de>
To: linux-kernel@vger.kernel.org
Cc: stable@linux.kernel.org
Subject: Re: Future of the -longterm kernel releases (i.e. how we pick them).
Date: Mon, 15 Aug 2011 08:48:22 +0200 [thread overview]
Message-ID: <4E48C136.6090306@web.de> (raw)
In-Reply-To: <20110815041524.GA7578@kroah.com>
Greg KH wrote, on 08/15/11 06:15:
<snip>
>
> - a new -longterm kernel is picked every year.
> - a -longterm kernel is maintained for 2 years and then dropped.
<snip>
Just a little nitpick: with this scheme you will accumulate longterm kernels. If
I understand it right, one longterm kernel is added every year.
next prev parent reply other threads:[~2011-08-15 6:48 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-15 4:15 Future of the -longterm kernel releases (i.e. how we pick them) Greg KH
2011-08-15 6:48 ` Jörg-Volker Peetz [this message]
2011-08-15 7:06 ` david
2011-08-15 7:16 ` Teck Choon Giam
2011-08-15 7:25 ` david
2011-08-15 7:38 ` Teck Choon Giam
2011-08-15 7:57 ` Jörg-Volker Peetz
2011-08-17 11:07 ` James Courtier-Dutton
2011-08-15 7:19 ` Jörg-Volker Peetz
2011-08-15 7:21 ` david
2011-08-15 14:21 ` Greg KH
2011-08-16 2:26 ` [Stable-review] " Ben Hutchings
2011-08-16 2:56 ` [stable] " Greg KH
2011-08-16 3:31 ` Ben Hutchings
2011-08-16 5:26 ` Daniel Taylor
2011-08-24 23:57 ` Greg KH
2011-08-15 7:33 ` [Stable-review] " Willy Tarreau
2011-08-15 14:18 ` [stable] " Greg KH
2011-08-15 15:04 ` [stable] " Tim Gardner
2011-08-16 2:09 ` [Stable-review] " Ben Hutchings
2011-08-16 2:57 ` [stable] " Greg KH
2011-08-16 19:26 ` Jeremiah C. Foster
2011-08-16 22:33 ` [stable] " Greg KH
2011-08-17 10:33 ` Jeremiah Foster
2011-08-17 20:20 ` david
2011-08-24 4:47 ` Greg KH
2011-08-24 4:46 ` Greg KH
2011-08-24 13:03 ` Jeremiah Foster
2011-08-16 23:01 ` Tim Bird
2011-08-17 4:58 ` Greg KH
2011-08-17 13:21 ` Mark Brown
2011-08-17 17:33 ` Brian Swetland
2011-08-24 4:57 ` Greg KH
2011-08-25 4:49 ` Brian Swetland
2011-08-26 0:03 ` Greg KH
2011-08-18 0:33 ` [Stable-review] " Ben Hutchings
2011-08-18 11:28 ` Pasi Kärkkäinen
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=4E48C136.6090306@web.de \
--to=jvpeetz@web.de \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@linux.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