From: Adrian Bunk <bunk@stusta.de>
To: Chuck Ebbert <cebbert@redhat.com>
Cc: Jesper Juhl <jesper.juhl@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Chris Wright <chrisw@sous-sol.org>
Subject: Re: 2.6.18-stable release plans?
Date: Tue, 23 Jan 2007 21:56:00 +0100 [thread overview]
Message-ID: <20070123205600.GD17836@stusta.de> (raw)
In-Reply-To: <45B6712C.2030901@redhat.com>
On Tue, Jan 23, 2007 at 03:33:48PM -0500, Chuck Ebbert wrote:
> Jesper Juhl wrote:
> > On 22/01/07, Chuck Ebbert <cebbert@redhat.com> wrote:
> >> Is there going to be another 2.6.18-stable release?
> >>
> >
> > Now that 2.6.19 is out, most likely not. -stable releases are made
> > for the latest stable 2.6.x kernel, once 2.6.x+1 is out that's the one
> > -stable patches are made for (2.6.16 is an exception)..
> >
> Great... just as 2.6.18 approaches actual stability.
>
> Adrian, how much longer are you going to support 2.6.16? Would you consider
> moving to 2.6.18 any time soon?
I'll continue to maintain 2.6.16 - moving to 2.6.18 or any other kernel
would defeat the purpose of what I am doing.
I'm not yet decided whether I'll create other stable kernel branches,
but it this will happen it won't be 2.6.18, more like 2.6.25 or 2.6.30.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2007-01-23 20:55 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-22 22:13 2.6.18-stable release plans? Chuck Ebbert
2007-01-23 0:23 ` Jesper Juhl
2007-01-23 13:38 ` [Proposal] " Sunil Naidu
2007-01-23 17:41 ` Stefan Richter
2007-01-23 19:25 ` Sunil Naidu
2007-01-23 20:06 ` Stefan Richter
2007-01-23 20:33 ` Chuck Ebbert
2007-01-23 20:56 ` Adrian Bunk [this message]
2007-01-24 4:50 ` Daniel Barkalow
-- strict thread matches above, loose matches on Subject: below --
2007-01-24 13:30 Chris Rankin
2007-01-24 14:37 ` Hugh Dickins
2007-01-24 15:06 Chris Rankin
2007-01-24 15:40 ` Hugh Dickins
2007-01-24 15:53 Chris Rankin
2007-01-24 16:12 ` Hugh Dickins
2007-01-24 17:33 ` Chris Rankin
2007-01-24 16:28 ` Mark Rustad
2007-01-24 22:37 ` Chris Rankin
2007-01-24 23:11 ` Alan
2007-01-24 23:05 ` Chris Rankin
2007-01-24 23:32 ` Mark Rustad
2007-01-24 23:45 ` Chris Rankin
2007-01-25 1:00 ` Ken Moffat
2007-01-25 9:16 ` Chris Rankin
2007-01-25 19:36 ` Ken Moffat
2007-01-26 13:02 ` Chris Rankin
2007-01-25 23:26 ` Alistair John Strachan
2007-01-25 3:05 ` Mark Rustad
2007-01-25 21:04 ` Matt Mackall
2007-02-02 4:02 ` Valdis.Kletnieks
2007-02-02 6:47 ` Jon Masters
2007-02-02 8:17 ` Valdis.Kletnieks
[not found] <BC3E207A-1A56-4032-9619-910E80281E9C@gmail.com>
2007-01-25 8:51 ` Chris Rankin
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=20070123205600.GD17836@stusta.de \
--to=bunk@stusta.de \
--cc=cebbert@redhat.com \
--cc=chrisw@sous-sol.org \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.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 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.