All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Dave Airlie <airlied@gmail.com>
Cc: Ben Hutchings <ben@decadent.org.uk>,
	Steven Rostedt <rostedt@goodmis.org>,
	ksummit-2013-discuss@lists.linuxfoundation.org,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [Ksummit-2013-discuss] KS Topic request: Handling the Stable kernel, let's dump the cc: stable tag
Date: Mon, 15 Jul 2013 23:23:02 -0700	[thread overview]
Message-ID: <20130716062302.GC19052@kroah.com> (raw)
In-Reply-To: <CAPM=9twPxz60WObwG5SuCxFrGTr7KzQyS3iqGnF8MQJPUZuHOg@mail.gmail.com>

On Tue, Jul 16, 2013 at 01:27:42PM +1000, Dave Airlie wrote:
> On Tue, Jul 16, 2013 at 12:41 PM, Ben Hutchings <ben@decadent.org.uk> wrote:
> > On Mon, 2013-07-15 at 22:09 -0400, Steven Rostedt wrote:
> > [...]
> >> > > How important is the stable releases? Are maintainers willing to do a
> >> > > little more work now to make sure their subsystems work fine in older
> >> > > kernels? This isn't the same stable as it was 8 years ago.
> >> >
> >> > And that annoys the hell out of some Linux companies who feel that the
> >> > stable kernels compete with them.  So people working for those companies
> >> > might not get as much help with doing any additional work for stable
> >> > kernel releases (this is not just idle gossip, I've heard it directly
> >> > from management's mouths.)
> >>
> >> Hmm, this is new to me. Really, I thought the whole point of the stable
> >> releases was to help Linux companies.
> > [...]
> >
> > I also heard some managers decided their kernel source packages should
> > have all the patches squashed together to make them harder to cherry-
> > pick... could it have been the same company?
> 
> Greg loves to tell stories about RH management, but really if he can
> find any engineer who works for RH that says he can't work on stable
> due to being told by management, I'd be surprised. Maybe when stable
> first surfaced there was a hope of it being close to RHEL, but at this
> point stable has little to no usefulness from a RHEL point of view,
> and since nearly all the RH employed maintainers all do stable work, I
> can't see why Greg would think this matters.
> 
> In fact Greg how much of stable queue does come from Red Hatters?

I always separate RH managers from engineers in their doings because I
know that one does not feel the same as the other.

My point is, if I start asking developers to do more work for the stable
trees, that has the potential to make people not like the stable trees
more for resource issues, and I don't want to do that at all.

greg k-h

  parent reply	other threads:[~2013-07-16  6:24 UTC|newest]

Thread overview: 72+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-15 19:27 KS Topic request: Handling the Stable kernel, let's dump the cc: stable tag James Bottomley
2013-07-15 19:45 ` [Ksummit-2013-discuss] " Steven Rostedt
2013-07-15 19:55   ` Willy Tarreau
2013-07-15 20:56     ` Steven Rostedt
2013-07-15 21:09       ` Joe Perches
2013-07-15 21:21         ` Steven Rostedt
2013-07-15 21:34           ` Joe Perches
2013-07-21  4:06         ` Rob Landley
2013-07-15 21:52       ` Willy Tarreau
2013-07-15 20:15   ` Mark Brown
2013-07-15 21:07     ` Steven Rostedt
2013-07-15 20:19 ` Guenter Roeck
2013-07-15 22:04   ` David Woodhouse
2013-07-15 22:07     ` Guenter Roeck
2013-07-15 22:38       ` H. Peter Anvin
2013-07-15 23:22         ` Guenter Roeck
2013-07-16  0:13           ` H. Peter Anvin
2013-07-16  0:21             ` Greg KH
2013-07-16  0:25               ` H. Peter Anvin
2013-07-16 15:50                 ` Paul Gortmaker
2013-07-15 20:20 ` Jason Cooper
2013-07-15 21:44 ` Greg KH
2013-07-15 21:55   ` Greg KH
2013-07-15 22:01     ` H. Peter Anvin
2013-07-15 23:08       ` Greg KH
2013-07-16  0:40         ` [Ksummit-2013-discuss] " Rafael J. Wysocki
2013-07-16  9:06       ` Jiri Kosina
2013-07-15 22:01   ` Steven Rostedt
2013-07-16  0:06     ` Greg KH
2013-07-16  2:09       ` Steven Rostedt
2013-07-16  2:41         ` Ben Hutchings
2013-07-16  3:27           ` Dave Airlie
2013-07-16  3:43             ` Steven Rostedt
2013-07-16  4:10             ` Ben Hutchings
2013-07-16  6:23             ` Greg KH [this message]
2013-07-16  6:10       ` James Bottomley
2013-07-16  6:28         ` Greg KH
2013-07-15 22:22   ` Jiri Kosina
2013-07-15 23:40     ` Jiri Kosina
2013-07-15 23:59     ` Greg KH
2013-07-16  2:30   ` Ben Hutchings
2013-07-16  6:13     ` Greg KH
2013-07-16  9:11       ` Jiri Kosina
2013-07-16 16:36         ` Greg KH
2013-07-17  3:53           ` Ben Hutchings
2013-07-17  4:24             ` Greg KH
2013-07-16  5:17   ` James Bottomley
2013-07-16  6:20     ` Greg KH
2013-07-16  7:43       ` [Ksummit-2013-discuss] " James Bottomley
2013-07-16  9:46         ` Jiri Kosina
2013-07-16  9:46           ` Jiri Kosina
2013-07-16 12:43           ` Ben Hutchings
2013-07-16 16:35           ` Greg KH
2013-07-16 23:15             ` Jiri Kosina
2013-07-16 13:14         ` Josh Boyer
2013-07-17 15:08         ` John W. Linville
2013-07-18  7:45           ` Kalle Valo
2013-07-16 10:02       ` Jan Kara
2013-07-16  6:24   ` David Lang
2013-07-16 16:45     ` [Ksummit-2013-discuss] " Steven Rostedt
2013-07-16  2:00 ` Ben Hutchings
2013-07-16  9:53   ` Mark Brown
2013-07-21  4:11 ` Rob Landley
2013-07-21 15:09   ` [Ksummit-2013-discuss] " Ben Hutchings
2013-07-22 21:24     ` KOSAKI Motohiro
2013-07-23  2:29       ` Li Zefan
2013-07-23  2:29         ` Li Zefan
2013-07-23  2:40 ` Myklebust, Trond
2013-07-23  2:40   ` Myklebust, Trond
2013-07-23  2:47   ` James Bottomley
2013-07-23  2:57     ` Myklebust, Trond
2013-07-23  2:57       ` Myklebust, Trond

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=20130716062302.GC19052@kroah.com \
    --to=greg@kroah.com \
    --cc=airlied@gmail.com \
    --cc=ben@decadent.org.uk \
    --cc=ksummit-2013-discuss@lists.linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=stable@vger.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.