From: Greg KH <greg@kroah.com>
To: CaT <cat@zip.com.au>
Cc: Chris Wright <chrisw@sous-sol.org>,
torvalds@osdl.org, Nigel Cunningham <ncunningham@cyclades.com>,
linux-kernel@vger.kernel.org, stable@kernel.org
Subject: Re: [stable] Re: Linux 2.6.16.14
Date: Thu, 4 May 2006 22:10:20 -0700 [thread overview]
Message-ID: <20060505051020.GA3869@kroah.com> (raw)
In-Reply-To: <20060505033325.GM4776@zip.com.au>
On Fri, May 05, 2006 at 01:33:25PM +1000, CaT wrote:
> On Thu, May 04, 2006 at 08:25:54PM -0700, Chris Wright wrote:
> > 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.
>
> I was wondering, will there be another/more stable .15 releases?
I don't think that Chris or I will be doing any, as we don't have any
pending patches against that tree that people have sent us. If you, or
someone else wants to take over the .15 tree, feel free :)
good luck,
greg k-h
next prev parent reply other threads:[~2006-05-05 5:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-05 0:35 Linux 2.6.16.14 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
2006-05-05 3:33 ` CaT
2006-05-05 5:10 ` Greg KH [this message]
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=20060505051020.GA3869@kroah.com \
--to=greg@kroah.com \
--cc=cat@zip.com.au \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.