mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: Greg KH <greg@kroah.com>
Cc: Chris Wright <chrisw@sous-sol.org>,
	stable-review@kernel.org, linux-kernel@vger.kernel.org,
	stable-review@linux.kernel.org
Subject: Re: 2.6.27 maintenance plans after 2.6.32 is released
Date: Tue, 8 Sep 2009 19:08:25 -0700	[thread overview]
Message-ID: <43e72e890909081908p64d243ffpef1d24281b485602@mail.gmail.com> (raw)
In-Reply-To: <20090908230416.GA8283@kroah.com>

On Tue, Sep 8, 2009 at 4:04 PM, Greg KH<greg@kroah.com> wrote:
> On Tue, Sep 08, 2009 at 12:44:23PM -0700, Luis R. Rodriguez wrote:
>> On Tue, Sep 8, 2009 at 12:30 PM, Luis R. Rodriguez<mcgrof@gmail.com> wrote:
>> > I was curious if 2.6.27 is planned to be supported after 2.6.32 is
>> > released, or will that be dropped in favor for 2.6.28 as the last
>> > supported kernel. How does dropping an old kernel for stable
>> > maintenance consideration typically work?
>
> .27 is a "long term" support kernel that I've decided to keep going for
> a variety of reasons.  .28 and .29 are currently no longer maintained.

Oh good to know, for some reason I expected we'd support 27..HEAD.

> So .27 is "special" right now, and seems to be working well.  I keep
> revaluating if it's worth keeping going, and so far, it seems like it
> is, if for nothing else, personal reasons as I have a few servers based
> on it :)
>
> For .30, we will probably do a few more releases once .31 is out, and
> then drop it as well.
>
> I'm confused as to what .32 has to do with any of this, that's months
> away...

I meant 31. Thanks for the explanation.

  Luis

      reply	other threads:[~2009-09-09  2:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-08 19:30 Luis R. Rodriguez
2009-09-08 19:44 ` Luis R. Rodriguez
2009-09-08 23:04   ` Greg KH
2009-09-09  2:08     ` Luis R. Rodriguez [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=43e72e890909081908p64d243ffpef1d24281b485602@mail.gmail.com \
    --to=mcgrof@gmail.com \
    --cc=chrisw@sous-sol.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable-review@kernel.org \
    --cc=stable-review@linux.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

all inboxes | Powered by JetHome®