mirror of
https://git.yoctoproject.org/meta-ti
synced 2026-07-16 22:38:04 +00:00
Koen Kooi
ebbeb55561
Also add script used to generate patches and SRC_URI Signed-off-by: Koen Kooi <koen@dominion.thruhere.net> Signed-off-by: Denys Dmytriyenko <denys@ti.com>
57 lines
2.4 KiB
Diff
57 lines
2.4 KiB
Diff
From 154964fb738a03a11e805252423a902b9c481c0f Mon Sep 17 00:00:00 2001
|
|
From: Joe Perches <joe@perches.com>
|
|
Date: Fri, 9 Dec 2011 14:12:00 -0800
|
|
Subject: [PATCH 02/49] Documentation: Update stable address
|
|
|
|
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(-)
|
|
|
|
diff --git a/Documentation/HOWTO b/Documentation/HOWTO
|
|
index 81bc1a9..f7ade3b 100644
|
|
--- 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.
|
|
diff --git a/Documentation/development-process/5.Posting b/Documentation/development-process/5.Posting
|
|
index 903a254..8a48c9b 100644
|
|
--- 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
|
|
--
|
|
1.7.9.4
|
|
|