From: Greg KH <greg@kroah.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>,
Adrian Bunk <bunk@kernel.org>,
Am??rico Wang <xiyou.wangcong@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
stable@kernel.org
Subject: Re: [stable] Linux 2.6.27 will be a longtime supported kernel
Date: Tue, 14 Oct 2008 16:23:42 -0700 [thread overview]
Message-ID: <20081014232342.GA1214@kroah.com> (raw)
In-Reply-To: <86802c440810141543q480a49c2x5e89afc542a61b1d@mail.gmail.com>
On Tue, Oct 14, 2008 at 03:43:26PM -0700, Yinghai Lu wrote:
> On Tue, Oct 14, 2008 at 2:04 PM, Greg KH <greg@kroah.com> wrote:
>
> > Fedora, Ubuntu, and openSUSE are going to be based on .27 from what I
> > can tell.
>
> opensuse 10.3 is 2.6.22
> opensuse 11 is 2.6.25
> so opensuse 12 will be 2.6.27? it is supposed to use 2.6.28, right?
openSUSE 11.1 will be 2.6.27. As it is to be released pretty soon now,
it would be a bit hard to base it off of .28 which isn't even out yet :)
thanks,
greg k-h
next prev parent reply other threads:[~2008-10-14 23:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-09 23:59 Linux 2.6.27 Linus Torvalds
2008-10-11 21:03 ` Linux 2.6.27 will be a longtime supported kernel Adrian Bunk
2008-10-12 4:02 ` [stable] " Greg KH
2008-10-12 4:10 ` Adrian Bunk
2008-10-12 7:00 ` Willy Tarreau
2008-10-13 11:27 ` Américo Wang
2008-10-13 12:37 ` Adrian Bunk
2008-10-14 20:10 ` Lennart Sorensen
2008-10-14 21:04 ` [stable] " Greg KH
2008-10-14 22:43 ` Yinghai Lu
2008-10-14 22:48 ` Jiri Kosina
2008-10-14 23:23 ` Greg KH [this message]
2008-10-14 23:03 ` Chris Friesen
2008-10-15 2:27 ` Greg KH
2008-10-13 12:42 ` Alex Howells
2008-10-13 12:58 ` Nick Piggin
2008-10-14 17:12 ` Chris Friesen
2008-11-13 22:46 ` Linux 2.6.27 Bill Davidsen
2008-11-14 15:30 ` Stefan Richter
2008-11-14 17:56 ` Bill Davidsen
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=20081014232342.GA1214@kroah.com \
--to=greg@kroah.com \
--cc=bunk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lsorense@csclub.uwaterloo.ca \
--cc=stable@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=xiyou.wangcong@gmail.com \
--cc=yinghai@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