From patchwork Tue Oct 18 07:33:19 2011 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: Re: [PATCH] Update email address for stable patch submission Date: Mon, 17 Oct 2011 21:33:19 -0000 From: Stefan Bader X-Patchwork-Id: 120371 Message-Id: <4E9D2BBF.8030002@canonical.com> To: Ubuntu Kernel Team So any mails to stable, as well as the CC: tag line should for future submissions be stable@vger.kernel.org. -Stefan -------- Original Message -------- Subject: Re: [PATCH] Update email address for stable patch submission Date: Mon, 17 Oct 2011 19:54:02 -0700 From: Greg KH To: David Rientjes CC: Josh Boyer , "David S. Miller" , linux-kernel@vger.kernel.org, stable@vger.kernel.org On Mon, Oct 17, 2011 at 06:37:48PM -0700, David Rientjes wrote: > On Mon, 17 Oct 2011, Josh Boyer wrote: > > > > Hmm, is stable@vger.kernel.org a replacement for stable@kernel.org or is > > > it just temporary until kernel.org is fully back to life? > > > > To my understanding, stable@kernel.org is now just a forward to > > stable@vger.kernel.org. > > Right, but the question is whether that's temporary or permanent. Permanent. > > Personally, I'd rather see the vger list take over entirely. However, > > that decision will remain in the more than capable hands of the admins. > > > > I'm wondering if we have the same replacement for x86@kernel.org which > I've received multiple bounces from (not sure if it currently is or not, I > haven't tried because of that recently) or things like security@kernel.org > or trivial@kernel.org. security@ will remain as-is, when it gets back up and working. I don't know about trivial@, I wasn't aware of that one. The mailman stuff for kernel.org is pretty far down the list of priority of what is being worked on. greg k-h --- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ or subsystem maintainer. @@ -35,10 +35,10 @@ Procedure for submitting patches to the -stable tree: cherry-picked than this can be specified in the following format in the sign-off area: - Cc: # .32.x: a1f84a3: sched: Check for idle - Cc: # .32.x: 1b9508f: sched: Rate-limit newidle - Cc: # .32.x: fd21073: sched: Fix affinity logic - Cc: # .32.x + Cc: # .32.x: a1f84a3: sched: Check for idle + Cc: # .32.x: 1b9508f: sched: Rate-limit newidle + Cc: # .32.x: fd21073: sched: Fix affinity logic + Cc: # .32.x Signed-off-by: Ingo Molnar The tag sequence has the meaning of: diff --git a/Documentation/stable_kernel_rules.txt b/Documentation/stable_kernel_rules.txt index e213f45..21fd05c 100644 --- a/Documentation/stable_kernel_rules.txt +++ b/Documentation/stable_kernel_rules.txt @@ -24,10 +24,10 @@ Rules on what kind of patches are accepted, and which ones are not, into the Procedure for submitting patches to the -stable tree: - Send the patch, after verifying that it follows the above rules, to - stable@kernel.org. You must note the upstream commit ID in the changelog - of your submission. + stable@vger.kernel.org. You must note the upstream commit ID in the + changelog of your submission. - To have the patch automatically included in the stable tree, add the tag - Cc: stable@kernel.org + Cc: stable@vger.kernel.org in the sign-off area. Once the patch is merged it will be applied to the stable tree without anything else needing to be done by the author