On Fri, Sep 05, 2014 at 03:36:26PM -0700, Greg Kroah-Hartman wrote: > > > If they apply cleanly, then just list the git commit ids, and I can take > > > care of the rest. > > > > OK. Is this a policy that should be documented? AIUI, we have a few > > options: > > > > 1. Include 'Cc: stable@xxxxxxxxxxxxxxx' in the original commit that > > gets to Linus > > > > 2. Send an email to stable@xxxxxxxxxxxxxxx that just contains the > > commit IDs, after they've made it to Linus > > > > 3. Send patches to stable@xxxxxxxxxxxxxxx, if backporting is not > > trivial > > > > #1 is most common, and #2 seems like it would handle most of what misses > > #1. #3 seems inferior, whenever #2 would suffice. But #2 is not in > > stable_kernel_rules.txt. > > I always gladly take patches to that .txt file if you wish to make it > clearer. I was interested in whether I had my facts straight before trying to document them. I'll take your response to mean I'm not far off base, so I'll take a stab at patching the file. Thanks, Brian -- 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