aboutsummaryrefslogtreecommitdiffstats
path: root/HOWTO
diff options
context:
space:
mode:
authorGreg Kroah-Hartman <gregkh@suse.de>2005-11-15 11:38:28 -0800
committerGreg Kroah-Hartman <gregkh@suse.de>2005-11-15 11:38:28 -0800
commitb6d4c837a60c00e7f011857c88f893ee7ab25d00 (patch)
tree7db6bd62163ba5a397aaaf754942fc6ffdabcd70 /HOWTO
parente0d1d74024639c31e34a22bd76cfa958464a8088 (diff)
downloadpatches-b6d4c837a60c00e7f011857c88f893ee7ab25d00.tar.gz
strip trailing spaces...
Diffstat (limited to 'HOWTO')
-rw-r--r--HOWTO12
1 files changed, 6 insertions, 6 deletions
diff --git a/HOWTO b/HOWTO
index ed9633e967d02..846662d3465d0 100644
--- a/HOWTO
+++ b/HOWTO
@@ -224,7 +224,7 @@ is as follows:
week.
- Process continues until the kernel is considered "ready", the
process should last around 6 weeks.
-
+
It is worth to mention what Andrew Morton wrote on the linux-kernel
mailing list about kernel releases:
"Nobody knows when a kernel will be released, because it's
@@ -242,7 +242,7 @@ regressions discovered in a given 2.6.x kernel.
This is the recommended branch for users who want the most recent stable
kernel and are not interested in helping test development/experimental
versions.
-
+
If no 2.6.x.y kernel is available, then the highest numbered 2.6.x
kernel is the current stable kernel.
@@ -273,13 +273,13 @@ the linux-kernel mailing list. This tree serves as a proving ground for
new features and patches. Once a patch has proved its worth in -mm for
a while Andrew or the subsystem maintainer pushes it on to Linus for
inclusion in mainline.
-
+
It is heavily encouraged that all new patches get tested in the -mm tree
before they are sent to Linus for inclusion in the main kernel tree.
These kernels are not appropriate for use on systems that are supposed
to be stable and they are more risky to run than any of the other
-branches.
+branches.
If you wish to help out with the kernel development process, please test
and use these kernel releases and provide feedback to the linux-kernel
@@ -288,7 +288,7 @@ mailing list if you have any problems, and if everything works properly.
These kernels in addition to all the other experimental patches they
contain usually also contain any changes in the mainline -git kernels
available at the time of release.
-
+
The -mm kernels are not released on a fixed schedule, but usually a few
-mm kernels are released in between each -rc kernel (1 to 3 is common).
@@ -301,7 +301,7 @@ different areas of the kernel. These trees are pulled into the -mm
kernel releases as described above.
Here is a list of some of the different kernel trees available:
- -
+ -
Bug Reporting