Re: [PATCH] A development process document, V2 (diff from V1)

[Stefan Richter <stefanr@s5r6.in-berlin.de>]

Jonathan Corbet wrote:
> --- a/Documentation/development-process/5.Posting
> +++ b/Documentation/development-process/5.Posting
...
> @@ -229,12 +235,18 @@ copies should go to:
...
>   - Send a copy to the relevant mailing list, or, if nothing else applies,
>     the linux-kernel list.
>  
> + - If you are fixing a bug, think about whether the fix should go into the
> +   next stable update.  If so, stable@kernel.org should get a copy of the
> +   patch.  Also add a "Cc: stable@kernel.org" to the tags within the patch

...patch after it or an equivalent was committed to Linus's tree.  Quote
the commit ID in your stable submission.  Alternatively, add a "Cc:
stable@...

> +   itself; that will cause the stable team to get a notification when your
> +   fix goes into the mainline.

Or IMO preferable:

 - If you are fixing a bug, think about whether the fix should go into
the next stable update.  If so, read ../stable_kernel_rules.txt.


(I missed the part of the thread where the addition of the -stable
bullet point was suggested, hence I may be saying something redundant
here...)
-- 
Stefan Richter
-=====-==--- =--- ----=
http://arcgraph.de/sr/