[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4892F27F.3020300@s5r6.in-berlin.de>
Date: Fri, 01 Aug 2008 13:24:47 +0200
From: Stefan Richter <stefanr@...6.in-berlin.de>
To: Jonathan Corbet <corbet@....net>
CC: LKML <linux-kernel@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Amanda McPherson <amanda@...pherson.com>,
Jiri Kosina <jkosina@...e.cz>,
Roland Dreier <rdreier@...co.com>,
Alex Chiang <achiang@...com>,
Jochen Voß <jochen.voss@...glemail.com>
Subject: Re: [PATCH] A development process document, V2 (diff from V1)
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@...nel.org should get a copy of the
> + patch. Also add a "Cc: stable@...nel.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/
--
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/
Powered by blists - more mailing lists