On Tue, Aug 20, 2013 at 05:49:24PM -0700, Greg KH wrote: > On Tue, Aug 20, 2013 at 08:41:23PM -0400, Josh Boyer wrote: > > On Tue, Aug 20, 2013 at 7:57 PM, Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx> wrote: > > >> I like this overall. The only thing I might change is "wait for -rc2" > > >> for patches tagged with CC: stable that go in during the merge window. > > >> It seems those are the ones that tend to bite us. > > > > > > Maintainers can always tag their patches to have me hold off until -rc2 > > > for that. > > > > They can (not immediately sure how though?) > > Some do: > Cc: stable <stable@xxxxxxxxxxxxxxx> # after -rc5 is out > or > Cc: stable <stable@xxxxxxxxxxxxxxx> # wait a -rc cycle > or > Cc: stable <stable@xxxxxxxxxxxxxxx> # wait a few weeks to bake That's where I think that the default one (with no indication) should be the higher delay. If the author has no clue about the emergency of his patch, who else can guess for him ? It's too optimistic to consider that some code authors will be realist about the impacts of their code. We all create bugs and regressions everywhere because we're sure about what we do, until someone says "hey dude you broke this". So if we expect authors to say "look, I managed to get this merged into mainline but I'm still not sure about the risks", I suspect only a small fraction of the patches will be tagged this way. But I may be wrong, after all it already works well with -net. Willy -- 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