On Thu, Jul 11, 2013 at 6:01 PM, Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx> wrote: > <rant> > 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. Very much agreed. > 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. This is the kind of stuff I was alluding to on the ksummit-discuss list. I was beginning to think we were the only ones noticing so I'm glad you're speaking up. > So, I've picked through the patches and dug out only those that I've > "guessed" at being more important than others for the 3.10.1 release. > I'll get to the rest of these after 3.11-rc1 is out, and eventually > they will make it into the stable releases, but I am going to be much > more strict as to what is being added (carriage return changes for > debug messages, really ACPI developers?) That's very much appreciated, Greg. Thanks. josh -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html