Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 2eb7f204 authored by Joe Perches's avatar Joe Perches Committed by Greg Kroah-Hartman
Browse files

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: default avatarJoe Perches <joe@perches.com>
Cc: stable <stable@vger.kernel.org>
Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>
parent bc7a2f3a
Loading
Loading
Loading
Loading
+2 −2
Original line number Original line Diff line number Diff line
@@ -275,8 +275,8 @@ versions.
If no 2.6.x.y kernel is available, then the highest numbered 2.6.x
If no 2.6.x.y kernel is available, then the highest numbered 2.6.x
kernel is the current stable kernel.
kernel is the current stable kernel.


2.6.x.y are maintained by the "stable" team <stable@kernel.org>, and are
2.6.x.y are maintained by the "stable" team <stable@vger.kernel.org>, and
released as needs dictate.  The normal release period is approximately 
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
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
security-related problem, instead, can cause a release to happen almost
instantly.
instantly.
+4 −4
Original line number Original line Diff line number Diff line
@@ -271,10 +271,10 @@ copies should go to:
   the linux-kernel list.
   the linux-kernel list.


 - If you are fixing a bug, think about whether the fix should go into the
 - 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
   next stable update.  If so, stable@vger.kernel.org should get a copy of
   patch.  Also add a "Cc: stable@kernel.org" to the tags within the patch
   the patch.  Also add a "Cc: stable@vger.kernel.org" to the tags within
   itself; that will cause the stable team to get a notification when your
   the patch itself; that will cause the stable team to get a notification
   fix goes into the mainline.
   when your fix goes into the mainline.


When selecting recipients for a patch, it is good to have an idea of who
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
you think will eventually accept the patch and get it merged.  While it