On Fri, Jul 12, 2013 at 01:57:18PM -0400, Theodore Ts'o wrote: > On Fri, Jul 12, 2013 at 10:28:36AM -0700, Greg Kroah-Hartman wrote: > > On Fri, Jul 12, 2013 at 10:20:46AM -0700, H. Peter Anvin wrote: > > > On the subject of the stable tree: could we get a standard format for > > > requesting post-inclusion elevation of patches to stable status? It > > > isn't all that unusual that the need for -stable is highlighted after a > > > patch has been included in a maintainer's tree, and rebasing to add > > > stable metadata annoys Linus. > > > > After it's in Linus's tree, just send the git id of the patch to > > stable@xxxxxxxxxxxxxxx, along with what stable tree(s) you want to see > > the patch backported to. > > > > Documentation/stable_kernel_rules.txt should be pretty explicit about > > how to do this, but if not, patches to it are always welcome. > > FWIW, Documentation/stable_kernel_rules.txt currently says that you > should send the patch. I checked to see whether sending the git id > was sufficient, and upon reading stable_kernel_rules.txt, decided to > simply run git format-patch/git send-email of the commits in mainline. > Apparently no one seemed to mind.... > That is what I do as well, with an added explicit reference to the upstream git id in the commit log. Guenter -- 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