Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756328Ab3GKW3t (ORCPT ); Thu, 11 Jul 2013 18:29:49 -0400 Received: from mx1.redhat.com ([209.132.183.28]:57971 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754982Ab3GKW3r (ORCPT ); Thu, 11 Jul 2013 18:29:47 -0400 Date: Thu, 11 Jul 2013 18:29:35 -0400 From: Dave Jones To: Greg Kroah-Hartman Cc: linux-kernel@vger.kernel.org, torvalds@linux-foundation.org, akpm@linux-foundation.org, stable@vger.kernel.org Subject: Re: [ 00/19] 3.10.1-stable review Message-ID: <20130711222935.GA11340@redhat.com> Mail-Followup-To: Dave Jones , Greg Kroah-Hartman , linux-kernel@vger.kernel.org, torvalds@linux-foundation.org, akpm@linux-foundation.org, stable@vger.kernel.org References: <20130711214830.611455274@linuxfoundation.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130711214830.611455274@linuxfoundation.org> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2119 Lines: 41 On Thu, Jul 11, 2013 at 03:01:17PM -0700, Greg Kroah-Hartman wrote: > > I'm sitting on top of over 170 more patches that have been marked for > the stable releases right now that are not included in this set of > releases. The fact that there are this many patches for stable stuff > that are waiting to be merged through the main -rc1 merge window cycle > is worrying to me. > > Why are subsystem maintainers holding on to fixes that are > _supposedly_ affecting all users? I mean, 21 powerpc core changes > that I don't see until a -rc1 merge? It's as if developers don't > expect people to use a .0 release and are relying on me to get the > fixes they have burried in their trees out to users. That's not that > nice. 6 "core" iscsi-target fixes? That's the sign of either a > broken subsystem maintainer, or a lack of understanding what the > normal -rc kernel releases are supposed to be for. I get the impression as soon as we hit -rc1, some maintainers immediately go into "OH SHIT, I CAN'T SEND PATCHES OR LINUS WILL SHOUT AT ME" mode. And the later in -rc we are, the more reluctant some people seem to be at sending stuff. Which, for slowing things down as we go through -rc is great, but not so much when people stop sending _everything_ and start thinking "I'll just get it in stable in a few weeks". For .10 I had to start making a list of "shit that's broken that there's an outstanding patch for" and nagging people to send them week after week. Every time I reported a new bug I'd hit, I'd have to explain I wasn't running Linus' tree because there was so much other crap I had to carry just to get things to a baseline of stability before starting tests. By rc7 things got a lot better, but if we have fixes sitting around in git trees for weeks on end with no progress, that kinda sucks. Dave -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/