public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Galbraith <efault@gmx.de>
To: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: Greg KH <greg@kroah.com>,
	stable@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: -longterm kernels
Date: Sun, 08 May 2011 07:09:21 +0200	[thread overview]
Message-ID: <1304831361.6326.21.camel@marge.simson.net> (raw)
In-Reply-To: <20110507145503.GA2276@redhat.com>

On Sat, 2011-05-07 at 16:55 +0200, Stanislaw Gruszka wrote:
> On Thu, May 05, 2011 at 08:25:01AM -0700, Greg KH wrote:
> > > BTW, Greg, perhaps -logterm releasing policy should be revised somehow.
> > > Currently we have .32, .33, .34, .35 -longterm, what is kind a much.
> > 
> > It's not "much" if you rely on that kernel version, right?
> 
> Yes, but maybe would be better if they do not relay on some versions in
> long term manner, and i.e. .33 users would use .32 and .34 users would
> use .35 instead?

Ceasing to rely upon .33 isn't a trivial choice for -rt tree users.

	-Mike


      parent reply	other threads:[~2011-05-08  5:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201105030110.p431A5W0005426@hera.kernel.org>
     [not found] ` <20110504223605.GA5967@kroah.com>
2011-05-05 14:58   ` -longterm kernels (Was: Re: [stable] Patch Upstream: iwlwifi: fix skb usage after free) Stanislaw Gruszka
2011-05-05 15:17     ` [stable] -longterm kernels (Was: " Willy Tarreau
2011-05-05 15:25     ` -longterm kernels (Was: Re: [stable] " Greg KH
2011-05-07 14:55       ` -longterm kernels Stanislaw Gruszka
2011-05-07 15:40         ` Greg KH
2011-05-07 15:57           ` Stanislaw Gruszka
2011-05-07 19:01             ` Greg KH
2011-05-09  9:18               ` Stanislaw Gruszka
2011-05-08  5:09         ` Mike Galbraith [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=1304831361.6326.21.camel@marge.simson.net \
    --to=efault@gmx.de \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sgruszka@redhat.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox