From: david@lang.hm
To: Jeremiah Foster <jeremiah@jeremiahfoster.com>
Cc: Greg KH <greg@kroah.com>, Ben Hutchings <ben@decadent.org.uk>,
linux-kernel@vger.kernel.org, stable@kernel.org,
akpm@linux-foundation.org, torvalds@linux-foundation.org,
stable-review@kernel.org, alan@lxorguk.ukuu.org.uk,
Debian kernel maintainers <debian-kernel@lists.debian.org>
Subject: Re: [stable] [Stable-review] Future of the -longterm kernel releases (i.e. how we pick them).
Date: Wed, 17 Aug 2011 13:20:37 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1108171313040.6543@asgard.lang.hm> (raw)
In-Reply-To: <056B8993-8B70-470A-AFDD-53F587AF3312@jeremiahfoster.com>
On Wed, 17 Aug 2011, Jeremiah Foster wrote:
>> Do they need help from the community
>> instead to help define, implement, and maintain this for them?
>
> I think the answer is yes.
>
to expand on this a bit.
it's a lot easier to look at changelogs and see if a -stable or -longterm
update is relavent to your systems than it is to watch the flood of
merges to the latest kerenl and then figure out how to backport them. BUt
people who start up just compiling their own kernels frequently become
testers, if not contributers to the kernel. If everyone only runs the
distro kernels, then the upstream kernel quality will suffer because
nobody is testing it.
people running -longterm kernels on their productionsystems will not be
testing the llatest -rc kernel on those systems, but they are likely to be
more interested in watching and testng new kernel releases (at least on
lab machines) than people who just wait for things to be backported to the
distro kernel.
David Lang
next prev parent reply other threads:[~2011-08-17 20:22 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-15 4:15 Greg KH
2011-08-15 6:48 ` Jörg-Volker Peetz
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 [this message]
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=alpine.DEB.2.02.1108171313040.6543@asgard.lang.hm \
--to=david@lang.hm \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ben@decadent.org.uk \
--cc=debian-kernel@lists.debian.org \
--cc=greg@kroah.com \
--cc=jeremiah@jeremiahfoster.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable-review@kernel.org \
--cc=stable@kernel.org \
--cc=torvalds@linux-foundation.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®