From: Chris Wright <chrisw@sous-sol.org>
To: Nigel Cunningham <ncunningham@cyclades.com>
Cc: Chris Wright <chrisw@sous-sol.org>,
linux-kernel@vger.kernel.org, stable@kernel.org,
torvalds@osdl.org
Subject: Re: Linux 2.6.16.14
Date: Thu, 4 May 2006 20:25:54 -0700 [thread overview]
Message-ID: <20060505032554.GC24291@moss.sous-sol.org> (raw)
In-Reply-To: <200605051303.37130.ncunningham@cyclades.com>
* Nigel Cunningham (ncunningham@cyclades.com) wrote:
> :) Tongue was firmly in cheek. I guess I should have said more initially. It
I figured it was a bit tongue in cheek ;-)
> wasn't so much the patch, as the speed with which they're coming. It makes me
> (at least) feel like the stable series is unstable. Couldn't you store them
> up for a day or two at a time (unless of course they really are that
> important that they require a quicker cycle).
Typically we do. The security patches tend to go out straight away,
unless they are very low risk, at which point they are batched with the
others. But once we know of a user triggerable security hole, it's
best to release rather than sit on it.
thanks,
-chris
next prev parent reply other threads:[~2006-05-05 3:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-05 0:35 Chris Wright
2006-05-05 0:42 ` Chris Wright
2006-05-05 1:52 ` Nigel Cunningham
2006-05-05 2:20 ` Ioan Ionita
2006-05-05 2:33 ` Chris Wright
2006-05-05 2:47 ` Alistair John Strachan
2006-05-08 19:02 ` Bill Davidsen
2006-05-09 19:18 ` [stable] " Chris Wright
2006-05-05 3:03 ` Nigel Cunningham
2006-05-05 3:18 ` Ioan Ionita
2006-05-05 3:42 ` Patrick McFarland
2006-05-05 3:25 ` Chris Wright [this message]
2006-05-05 3:33 ` CaT
2006-05-05 5:10 ` [stable] " Greg KH
2006-05-05 4:50 ` Willy Tarreau
2006-05-05 5:02 ` Nigel Cunningham
2006-05-05 5:20 ` Willy Tarreau
2006-05-05 13:29 ` Josh Boyer
2006-05-05 17:40 ` Chris Wright
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=20060505032554.GC24291@moss.sous-sol.org \
--to=chrisw@sous-sol.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ncunningham@cyclades.com \
--cc=stable@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
Powered by JetHome