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

[Greg KH]

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@xxxxxxxxxxx If the tag (Cc: stable@xxxxxxxxxx) 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@xxxxxxxxxxxxx>
> ---
> 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@xxxxxxxxxxx
> +   stable@xxxxxxxxxxx An alternative is to have the tag
> +    Cc: stable@xxxxxxxxxx
> +   in the sign-off area. Once the patch is merged it will be filtered
> +   into the stable tree even without sending directly to
> +   stable@xxxxxxxxxx

This is already documented (somewhat poorly) in the paragraph a few
bullets below this one that says:
	 - If the stable@xxxxxxxxxx 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@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/