public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Greg KH <greg@kroah.com>
Cc: stable@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: -longterm kernels
Date: Mon, 9 May 2011 11:18:17 +0200	[thread overview]
Message-ID: <20110509091815.GA3138@redhat.com> (raw)
In-Reply-To: <20110507190124.GA18913@kroah.com>

On Sat, May 07, 2011 at 12:01:24PM -0700, Greg KH wrote:
> On Sat, May 07, 2011 at 05:57:50PM +0200, Stanislaw Gruszka wrote:
> > On Sat, May 07, 2011 at 08:40:40AM -0700, Greg KH wrote:
> > > Nope, I'm not making such a rule, as you are trying to tell others what
> > > to do here.  And I'm not going to do that.
> > 
> > That was only a proposition, telling you what to do was not my intention.
> 
> Ah, but that's the main issue here.
> 
> It's a matter of people stepping up and doing things, not setting rules
> for what others are to maintain, right?

Right. I quite realize, that I should wrote "I like to maintain regular
longterm kernel releases, what you think?", but well ... my todo queue
is bigger and bigger instead of being smaller - I can not take such task
now, nor in the near future.

I just wanted to share idea about regular longterm releases. Having also
maintainers time in mind. Taking into account that in last time -longterm
kernels arise like mushrooms after the rain, I can imagine that soon
maintained -longterm versions would be i.e. 32,33,34,35,42,43,44,45.
Having 32,35,38,41,44 instead could save maintainers as well as
developers time.

Anyway, I didn't want to tell anyone what to do. Apologize that my posts
sounded that way.

> Back to one of your points, is Red Hat somehow not aware of the current
> stable/longterm situation and wishes to have things change here?  Last
> time I discussed this with the kernel maintainers there, they were fine
> with how things are working, has this now changed?

No, I only speak for myself here not Red Hat at all nor any other RH
employee, all I wrote in this thread were my opinions and ideas.

Thanks
Stanislaw

  reply	other threads:[~2011-05-09  9:18 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 [this message]
2011-05-08  5:09         ` Mike Galbraith

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=20110509091815.GA3138@redhat.com \
    --to=sgruszka@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox