Hi Shawn, On Mon, Aug 27 2012, Shawn Guo wrote: >>> On 28 August 2012 07:07, Chris Ball <cjb@xxxxxxxxxx> wrote: >>>> Thanks, pushed to mmc-next for 3.6. (stable@ shouldn't be CC'd.) >>>> >>> I categorised it as a fix for a regression. >> > It means not only for stable but also for -rc series rather than -next. Sure; I've already applied it to mmc-next for 3.6. > Doing this strictly means people have to keep tracking if the fix hits > mainline and remember to resubmit it to stable afterwards. Should > subsystem maintainer or author be that people? It's not easy anyway. No, the stable team look for patches entering mainline with "Cc: stable@xxxxxxxxxxxxxxx" in the commit message, and apply them to stable@ at that point. That's the right time to apply them. So, as I understand it, you did the right thing in having "Cc: <stable@xxxxxxxxxxxxxxx>" inside your commit message, and the wrong thing in sending the mail to stable@ at the same time. That's why I removed it from CC. Thanks, - Chris. -- Chris Ball <cjb@xxxxxxxxxx> <http://printf.net/> One Laptop Per Child -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
