[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070205221233.GU10475@sequoia.sous-sol.org>
Date: Mon, 5 Feb 2007 14:12:33 -0800
From: Chris Wright <chrisw@...s-sol.org>
To: Greg KH <greg@...ah.com>
Cc: Michael Krufky <mkrufky@...uxtv.org>,
Chris Wright <chrisw@...s-sol.org>, torvalds@...l.org,
akpm@...l.org, "Theodore Ts'o" <tytso@....edu>,
Zwane Mwaikambo <zwane@....linux.org.uk>,
Justin Forbes <jmforbes@...uxtx.org>,
linux-kernel@...r.kernel.org,
Chris Wedgwood <reviews@...cw.f00f.org>,
Randy Dunlap <rdunlap@...otime.net>,
Dave Jones <davej@...hat.com>,
Chuck Wolber <chuckw@...ntumlinux.com>, stable@...nel.org,
alan@...rguk.ukuu.org.uk
Subject: Re: [stable] [patch 00/50] -stable review
* Greg KH (greg@...ah.com) wrote:
> On Sun, Feb 04, 2007 at 01:24:18PM -0500, Michael Krufky wrote:
> > At which point was 2.6.18.y dropped? I thought we were always going to keep
> > the last two stable kernels up-to-date.
Not quite. It's more of a "some overlap," so that as soon as 2.6.x
comes out we don't instantly drop 2.6.(x-1).y stream. But we don't keep
it going, typically more 1 or 2 2.6.(x-1).y releases once 2.6.x is out.
> > Have I been wasting my time fwd'ing
> > 2.6.18.y patches?
I had actually queued them up, but we only had 1 or 2 other patches,
and they weren't significant enough to warrant flushing that queue.
thanks,
-chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists