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>
Loading branch information
2 changed files
and 6 deletions.
@@ -275,8 +275,8 @@ versions.
If no 2.6.x.y kernel is available, then the highest numbered 2.6.x
kernel is the current stable kernel.
-2.6.x.y are maintained by the "stable" team <email@example.com>, and
-released as needs dictate. The normal release period is approximately
+2.6.x.y are maintained by the "stable" team <stable@
are released as needs dictate. The normal release period is approximately
two weeks, but it can be longer if there are no pressing problems. A
security-related problem, instead, can cause a release to happen almost
@@ -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, firstname.lastname@example.org should get a copy of
- patch. Also add a "Cc: email@example.com" to the tags within
- itself; that will cause the stable team to get a notification
- fix goes into the mainline.
+ next stable update. If so, stable@
vger.kernel.org should get a copy of
the patch. Also add a "Cc: stable@ vger.kernel.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