| 1 |
dsd 07/11/06 23:11:34 |
| 2 |
|
| 3 |
Modified: maintenance.xml |
| 4 |
Log: |
| 5 |
add linux-stable documentation |
| 6 |
|
| 7 |
Revision Changes Path |
| 8 |
1.2 xml/htdocs/proj/en/kernel/maintenance.xml |
| 9 |
|
| 10 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/kernel/maintenance.xml?rev=1.2&view=markup |
| 11 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/kernel/maintenance.xml?rev=1.2&content-type=text/plain |
| 12 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/kernel/maintenance.xml?r1=1.1&r2=1.2 |
| 13 |
|
| 14 |
Index: maintenance.xml |
| 15 |
=================================================================== |
| 16 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/kernel/maintenance.xml,v |
| 17 |
retrieving revision 1.1 |
| 18 |
retrieving revision 1.2 |
| 19 |
diff -u -r1.1 -r1.2 |
| 20 |
--- maintenance.xml 30 Apr 2007 02:10:08 -0000 1.1 |
| 21 |
+++ maintenance.xml 6 Nov 2007 23:11:34 -0000 1.2 |
| 22 |
@@ -819,15 +819,42 @@ |
| 23 |
</section> |
| 24 |
</chapter> |
| 25 |
|
| 26 |
+ |
| 27 |
<chapter> |
| 28 |
<title>genpatches and linux-stable</title> |
| 29 |
+ |
| 30 |
+<section> |
| 31 |
+<title>Submission criteria</title> |
| 32 |
+<body> |
| 33 |
+ |
| 34 |
+<ul> |
| 35 |
+<li>This section is aimed at documenting the process for Gentoo kernel developers only (rather than just prospective ones), but if you're really keen, feel free to ask on IRC if you'd like to submit a patch.</li> |
| 36 |
+<li>The patch must conform to the stable kernel rules, see Documentation/stable_kernel_rules.txt</li> |
| 37 |
+<li>The patch must have been shipped in at least one gentoo-sources release. The reasoning here is that some of the time, patches committed to genpatches are untested -- full testing is carried out before release.</li> |
| 38 |
+<li>The patch must not already be in the stable queue. Check the |
| 39 |
+<uri link="http://git.kernel.org/?p=linux/kernel/git/stable/stable-queue.git;a=tree">stable-queue.git web interface</uri>.</li> |
| 40 |
+</ul> |
| 41 |
+ |
| 42 |
+</body> |
| 43 |
+</section> |
| 44 |
+ |
| 45 |
<section> |
| 46 |
+<title>Submission process</title> |
| 47 |
<body> |
| 48 |
|
| 49 |
<p> |
| 50 |
-to be written later |
| 51 |
+Prepare an email in the following way: |
| 52 |
</p> |
| 53 |
|
| 54 |
+<ul> |
| 55 |
+<li>Addressed to stable@××××××.org</li> |
| 56 |
+<li>CC kernel@g.o</li> |
| 57 |
+<li>CC the patch author, who's contact details can be found in the patch</li> |
| 58 |
+<li>Use the same subject line as the one in the patch, prepended with [PATCH] if it is not there already.</li> |
| 59 |
+<li>In the message body, include a very brief description with a reference to the Gentoo bug report, for example: This patch fixes a bootup crash in the snd-intel-hda driver as detailed at http://bugs.gentoo.org/12345</li> |
| 60 |
+<li><e>Attach</e> the patch to the email, directly from genpatches. The patch should have come from gitweb or similar and already have the authorship details, commit ID, etc.</li> |
| 61 |
+</ul> |
| 62 |
+ |
| 63 |
</body> |
| 64 |
</section> |
| 65 |
</chapter> |
| 66 |
|
| 67 |
|
| 68 |
|
| 69 |
-- |
| 70 |
gentoo-commits@g.o mailing list |
Archives