|author||Joe Perches <firstname.lastname@example.org>||2011-12-09 14:12:00 -0800|
|committer||Greg Kroah-Hartman <email@example.com>||2011-12-12 14:14:31 -0800|
Documentation: Update stable address
The Japanese/Korean/Chinese versions still need updating. Also, the stable kernel 2.6.x.y descriptions are out of date and should be updated as well. Signed-off-by: Joe Perches <firstname.lastname@example.org> Cc: stable <email@example.com> Signed-off-by: Greg Kroah-Hartman <firstname.lastname@example.org>
Diffstat (limited to 'Documentation/development-process/5.Posting')
1 files changed, 4 insertions, 4 deletions
diff --git a/Documentation/development-process/5.Posting b/Documentation/development-process/5.Posting
index 903a2546f138..8a48c9b62864 100644
@@ -271,10 +271,10 @@ copies should go to:
the linux-kernel list.
- If you are fixing a bug, think about whether the fix should go into the
- next stable update. If so, email@example.com should get a copy of the
- patch. Also add a "Cc: firstname.lastname@example.org" to the tags within the patch
- itself; that will cause the stable team to get a notification when your
- fix goes into the mainline.
+ next stable update. If so, email@example.com should get a copy of
+ the patch. Also add a "Cc: firstname.lastname@example.org" to the tags within
+ the patch itself; that will cause the stable team to get a notification
+ when your fix goes into the mainline.
When selecting recipients for a patch, it is good to have an idea of who
you think will eventually accept the patch and get it merged. While it