linux-kernel - Re: [PATCH] Doc/stable rules: add new cherry-pick logic

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 4 Dec 2009 08:41:26 -0800
From:	Greg KH <gregkh@...e.de>
To:	Sebastian Andrzej Siewior <sebastian@...akpoint.cc>
Cc:	Artem Bityutskiy <Artem.Bityutskiy@...ia.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] Doc/stable rules: add new cherry-pick logic

On Fri, Dec 04, 2009 at 12:16:35PM +0100, Sebastian Andrzej Siewior wrote:
> - it is possible to submit patches for the stable queue without sending
>   them directly stable@...nel.org. If the tag (Cc: stable@...nel.org) is
>   available in the sign-off area then hpa's script will filter them into
>   the stable mailbox once it hits Linus' tree.
> - Patches which require others to be applied first can be also specified.
>   This was discussued in http://lkml.org/lkml/2009/11/9/474
> 
> Signed-off-by: Sebastian Andrzej Siewior <sebastian@...akpoint.cc>
> ---
> Greg, the cherry pick format got acked by stable team didn't it?
> 
>  Documentation/stable_kernel_rules.txt |   22 +++++++++++++++++++++-
>  1 files changed, 21 insertions(+), 1 deletions(-)
> 
> diff --git a/Documentation/stable_kernel_rules.txt b/Documentation/stable_kernel_rules.txt
> index a452227..8c0aaad 100644
> --- a/Documentation/stable_kernel_rules.txt
> +++ b/Documentation/stable_kernel_rules.txt
> @@ -25,7 +25,27 @@ 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@...nel.org.
> +   stable@...nel.org. An alternative is to have the tag
> +    Cc: stable@...nel.org
> +   in the sign-off area. Once the patch is merged it will be filtered
> +   into the stable tree even without sending directly to
> +   stable@...nel.org

This is already documented (somewhat poorly) in the paragraph a few
bullets below this one that says:
	 - If the stable@...nel.org address is added to a patch, when it
	   goes into Linus's tree it will automatically be emailed to
	   the stable team.

Can you delete this paragraph, as your documentation is much nicer and
makes more sense?

Care to redo this patch that way?

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/