> On Sunday 14 of October 2012 10:27:22 Rafael J. Wysocki wrote: > > Hi, > > > > Thanks for the patch! I'll queue it up for v3.7 when I get back home from > > the current trip (around the -rc3 time frame I suppose). > > > > In future please don't send patches directly to stable@xxxxxxxxxxxxxxx. > > That doesn't make -stable pick them up anyway and confuses things. > > That happens anyway if you tag the patch for stable and use git > send-email. Unless you go the extra mile and filter out the cc list, > which is tedious. Well, please don't tag patches for -stable, because -stable doesn't take _patches_. It takes commits from the Linus' tree and backports them and that's maintainer's job to tag them for -stable, not yours. You can give the maintainer a hint that you _think_ it's -stable material (e.g. in the additional patch description that goes after the changelog), but the maintainer may still disagree with you and may not tag the commit for -stable after all. > Besides, I'm pretty sure stable maintainers verify a patch is actually > upstream before applying it anyway. Yes, they do, but that means it doesn't make sense to send them stuff before it's been merged, right? Rafael -- I speak only for myself. Rafael J. Wysocki, Intel Open Source Technology Center. -- To unsubscribe from this list: send the line "unsubscribe cpufreq" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
