Techwizz/kernel-fxtec-pro1x
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Documentation: Update stable address

Browse source 
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 <joe@perches.com>
Cc: stable <stable@vger.kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
This commit is contained in:
Joe Perches 2011-12-09 14:12:00 -08:00 committed by Greg Kroah-Hartman
parent bc7a2f3abc
commit 2eb7f204db
2 changed files with 6 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
Documentation/HOWTO
View file

@ -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.

8
Documentation/development-process/5.Posting
View file

@ -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