lkml.org 
[lkml]   [2012]   [Jan]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    Patch in this message
    /
    Date
    From
    Subject[02/40] Documentation: Update stable address
    3.0-stable review patch.  If anyone has any objections, please let me know.

    ------------------

    From: Joe Perches <joe@perches.com>

    commit 2eb7f204db51969ea558802a6601d79c2fb273b9 upstream.

    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>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>

    ---
    Documentation/HOWTO | 4 ++--
    Documentation/development-process/5.Posting | 8 ++++----
    2 files changed, 6 insertions(+), 6 deletions(-)

    --- a/Documentation/HOWTO
    +++ b/Documentation/HOWTO
    @@ -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 <stable@kernel.org>, and are
    -released as needs dictate. The normal release period is approximately
    +2.6.x.y are maintained by the "stable" team <stable@vger.kernel.org>, and
    +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
    instantly.
    --- a/Documentation/development-process/5.Posting
    +++ b/Documentation/development-process/5.Posting
    @@ -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, stable@kernel.org should get a copy of the
    - patch. Also add a "Cc: stable@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.
    + 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



    \
     
     \ /
      Last update: 2012-01-10 23:59    [W:0.023 / U:0.104 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site