All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Américo Wang" <xiyou.wangcong@gmail.com>
To: Geoffrey Said <geoffrey@2x.com>
Cc: "Américo Wang" <xiyou.wangcong@gmail.com>,
	stable@kernel.org, linux-kernel@vger.kernel.org, greg@kroah.com
Subject: Re: Long maintenance kernel versions.
Date: Fri, 24 Sep 2010 17:29:29 +0800	[thread overview]
Message-ID: <20100924092929.GC5453@cr0.nay.redhat.com> (raw)
In-Reply-To: <AANLkTimDtYF_ZNGvH-UxWrFyMsxjzKfsgyDTJnjt70Hs@mail.gmail.com>

On Fri, Sep 24, 2010 at 07:42:50AM +0200, Geoffrey Said wrote:
>Thanks for the prompt reply,
>
>but this puts us at a disadvantage as we will not know which kernel
>will be long term supported when starting the development process.
>

That is true, unfortunately.


>Take our case for the 34 kernel.  I knew that SuSE were going to use
>the 34 kernel in their 11.3 and since it was the latest we started
>work on the integration.  Now after the work is almost over, we hear
>that it will not be maintained anymore and we need to move to 35.  I
>do not think that this is a good system for people like us which have
>limited resources at their disposal.
>

Why not just pick .32? And backport features from 34 to 32.
That should not be hard.


>Can I suggest that their is a road map and long term maintenance
>kernels are ear marked before hand by the major Linux distributions?
>This will enable us to wait and integrate kernels fully confident that
>they will be long term supported.
>

I think Greg is the right person to answer this question. :)

Thanks!

  parent reply	other threads:[~2010-09-24  9:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-24  5:10 Long maintenance kernel versions Geoffrey Said
2010-09-24  5:36 ` Américo Wang
2010-09-24  5:42   ` Geoffrey Said
2010-09-24  8:54     ` el es
2010-09-24  9:29     ` Américo Wang [this message]
2010-09-24 13:19 ` Greg KH
2010-09-24 13:30   ` Geoffrey Said
2010-09-24 13:48     ` Greg KH

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=20100924092929.GC5453@cr0.nay.redhat.com \
    --to=xiyou.wangcong@gmail.com \
    --cc=geoffrey@2x.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@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.