On Fri, Jul 12, 2013 at 11:22:23PM -0700, Greg Kroah-Hartman wrote: > > So probably we should incite patch contributors to add a specific > > tag such as "Fixes: 3.5 and later", so that non-important patches > > do not need the Cc:stable anymore, but users who experience an issue > > can easily spot them and ask for their inclusion. > > Huh? What's wrong with the existing way people mark stable patches to > go back to much older kernel versions? Is that not working well enough > for you? > > And if something "fixes" an issue, then I want it in stable, just like > Linus wants that in his tree. It's the difference between "this is a fix" and "please backport this fix into stable". As we aid in this thread, cc:stable is a bit too much automatic and sometimes not appropriate (not important enough fixes). But when fixes not apparently suitable for stable are merged into mainline, having the ability to spot them is useful, whether it is for later inclusion or just for users who'd like to run a kernel with more fixes than the critical ones accepted for stable. > Don't add another tag that requires users to dig for fixes that we are > just too lazy to be including for all users, that way is crazy. I don't think so. If there is a gap between what is fixed and what is acceptable for -stable, this just fills this gap. It means less automatic submissions for -stable, only the important ones, and at the same time, a simple way of more easily spotting if a known bug affects your kernel when you're a -stable user and are experiencing an issue. 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