[kernel] r6106 - dists/trunk/docs

[maximilian attems]

Author: maks-guest
Date: Wed Mar  8 14:56:58 2006
New Revision: 6106

Modified:
   dists/trunk/docs/bits_kernel_team_0306.txt
Log:
tw=74


Modified: dists/trunk/docs/bits_kernel_team_0306.txt
==============================================================================
--- dists/trunk/docs/bits_kernel_team_0306.txt	(original)
+++ dists/trunk/docs/bits_kernel_team_0306.txt	Wed Mar  8 14:56:58 2006
@@ -20,17 +20,17 @@
 As mentioned above, we are tracking upstream closely.  Usually, the latest
 upstream release reaches unstable almost on the day of its release.
 Experimental acts as staging area, where the -rcX kernels are built.  If
-you want to be on the cutting edge, Bastian Blank provides daily builds out
-of the debian-kernel repository [1].
+you want to be on the cutting edge, Bastian Blank provides daily builds
+out of the debian-kernel repository [1].
 
 There has been lots of excitement around the x86 SMP alternatives patch,
 which would allow to reduce the current number of flavors. SMP hardware
 would just be a special case of hotplug CPUs. The uniprocessor flavors
 would also support SMP and the SMP ones could be dropped. On the feature
-side there is work going on to add vserver, Xen and UML flavors to
-linux-2.6.  Most legacy Debian specific patches have been cleared,
-the bulk of the current patchset is arch specific. 2.6 arch support is
-growing from release to release, so those patchsets should be of no concern.
+side there is work going on to add VServer, Xen and UML flavors to
+linux-2.6.  Most legacy Debian specific patches have been cleared, the
+bulk of the current patchset is arch specific. 2.6 arch support is growing
+from release to release, so those patchsets should be of no concern.
 
 2.6 Linux features initramfs, which contains the boot-relevant drivers.
 Currently there are two different supported tools for generating the
@@ -52,12 +52,12 @@
 
 Security
 ~~~~~~~~
-Dann Frazier, Simon Horman, and Moritz Muehlenhoff are doing a marvelous job in
-scanning and testing all CVEs (Common Vulnerabilities and Exposures, a unique
-ID for security issues) which get issued against the Linux kernel.  The second
-round of the sarge Debian kernel is prepared [3] and has been submitted to the
-stable security team. You won't believe it, but there is even a round for woody
-prepared [4].
+Dann Frazier, Simon Horman, and Moritz Muehlenhoff are doing a marvelous
+job in scanning and testing all CVEs (Common Vulnerabilities and
+Exposures, a unique ID for security issues) which get issued against the
+Linux kernel.  The second round of the sarge Debian kernel is prepared [3]
+and has been submitted to the stable security team. You won't believe it,
+but there is even a round for woody prepared [4].
 
 End of line
 ~~~~~~~~~~~
@@ -74,13 +74,13 @@
 
 Documentation
 ~~~~~~~~~~~~~
-The Debian Linux kernel handbook [5] contains lots of information
-about the Debian Linux kernel packages, recommended procedures, and
-other Debian-specific kernel-related information.  There you'll also
-find some practical chapters like "Filing a bug against a kernel
-package".  The kernel-handbook is currently a "work in progress", so
-any contributions, suggestions and corrections are very welcome.  They
-should be submitted to the kernel-handbook mailing list [6].
+The Debian Linux kernel handbook [5] contains lots of information about
+the Debian Linux kernel packages, recommended procedures, and other
+Debian-specific kernel-related information.  There you'll also find some
+practical chapters like "Filing a bug against a kernel package".  The
+kernel-handbook is currently a "work in progress", so any contributions,
+suggestions and corrections are very welcome.  They should be submitted to
+the kernel-handbook mailing list [6].
 
 Cheers,