linux-kernel - Re: [PATCH] Documentation: -stable rules: upstream commit ID requirement reworded

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Fri, 2 Apr 2010 09:11:18 -0700
From:	Randy Dunlap <rdunlap@...otime.net>
To:	Stefan Richter <stefanr@...6.in-berlin.de>
Cc:	Greg KH <gregkh@...e.de>, David Miller <davem@...emloft.net>,
	Willy Tarreau <w@....eu>, linux-kernel@...r.kernel.org,
	linux-doc@...r.kernel.org
Subject: Re: [PATCH] Documentation: -stable rules: upstream commit ID
 requirement reworded

On Thu, 1 Apr 2010 22:01:52 +0200 (CEST) Stefan Richter wrote:

> It is a hard requirement to include the upstream commit ID in the
> changelog of a -stable submission, not just a courtesy to the stable
> team.  This concerns only mail submission though, which is no longer
> the only way into stable.  (Also, fix a double "the".)
> 
> Signed-off-by: Stefan Richter <stefanr@...6.in-berlin.de>

Looks good to me.  Thanks.

Acked-by: Randy Dunlap <rdunlap@...otime.net>


> ---
>  Documentation/stable_kernel_rules.txt |    9 ++++-----
>  1 file changed, 4 insertions(+), 5 deletions(-)
> 
> Index: b/Documentation/stable_kernel_rules.txt
> ===================================================================
> --- a/Documentation/stable_kernel_rules.txt
> +++ b/Documentation/stable_kernel_rules.txt
> @@ -18,16 +18,15 @@ Rules on what kind of patches are accept
>   - It cannot contain any "trivial" fixes in it (spelling changes,
>     whitespace cleanups, etc).
>   - It must follow the Documentation/SubmittingPatches rules.
> - - It or an equivalent fix must already exist in Linus' tree.  Quote the
> -   respective commit ID in Linus' tree in your patch submission to -stable.
> + - It or an equivalent fix must already exist in Linus' tree (upstream).
>  
>  
>  Procedure for submitting patches to the -stable tree:
>  
>   - Send the patch, after verifying that it follows the above rules, to
> -   stable@...nel.org.
> - - To have the patch automatically included in the stable tree, add the
> -   the tag
> +   stable@...nel.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@...nel.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


---
~Randy
--
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/