public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Rene Rebe <rene@exactcode.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.16.47-rc1
Date: Wed, 11 Apr 2007 20:01:40 +0200	[thread overview]
Message-ID: <20070411180140.GE10141@stusta.de> (raw)
In-Reply-To: <200704111834.32705.rene@exactcode.de>

On Wed, Apr 11, 2007 at 06:34:32PM +0200, Rene Rebe wrote:

> Hi Adrian,

Hi René,

> first front off: thanks for the phantastic 2.6.16 stable maintenance.
> 
> Currently I wonder if you have any plan for doing the 2.6.16 review
> for let's say "years", or if you "soon" pick some new series such as
> 2.6.20 or so for long-term maintenance.

I'm not yet decided whether I'll do the same for some future kernel, but 
even if I'll do it, that wouldn't imply an immediate dropping of the 
2.6.16 series - especially since in a "security fixes only" mode 
maintaining it would require nearly zero work.

> I ask because I wonder if I should wait a bit with a production 2.6.17
> kernel line I maintain right now for just one installation base, if you
> choose some 2.6.2x I can hop on, or whether it is wiser to just downdate
> this series and profit from the "long-term" 2.6.16 maintenance that is
> no fun to replicate for 2.6.17 just for this one install pool ...

If I'll maintain a more recent kernel series, that would be >= 2.6.22.
So if you need something in the near future that wouldn't help you.

If 2.6.16 works for you that sounds like a good option, otherwise you 
could get security support [1] by building upon some distribution kernel 
(e.g. Ubuntu 6.10 that will get security updates for the next 12 months 
ships with a 2.6.17 kernel).

> Thanks in advance,

cu
Adrian

[1] and that's what the "long-term maintenance" of 2.6.16 is really
    about: no regressions and security fixes

-- 

       "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


      reply	other threads:[~2007-04-11 18:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-11 14:14 Linux 2.6.16.47-rc1 Adrian Bunk
2007-04-11 16:34 ` Rene Rebe
2007-04-11 18:01   ` Adrian Bunk [this message]

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=20070411180140.GE10141@stusta.de \
    --to=bunk@stusta.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rene@exactcode.de \
    /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