[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1457314578-23569-1-git-send-email-phil@philippeloctaux.com>
Date: Mon, 7 Mar 2016 02:36:18 +0100
From: Philippe Loctaux <phil@...lippeloctaux.com>
To: corbet@....net
Cc: gregkh@...uxfoundation.org, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org,
Philippe Loctaux <phil@...lippeloctaux.com>
Subject: [PATCH] Documentation: Howto: Fixed subtitles style
Fixed subtitles style, aligned them with their header.
Signed-off-by: Philippe Loctaux <phil@...lippeloctaux.com>
---
Documentation/HOWTO | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/Documentation/HOWTO b/Documentation/HOWTO
index d5a699d..109ec84 100644
--- a/Documentation/HOWTO
+++ b/Documentation/HOWTO
@@ -68,7 +68,7 @@ For common questions and answers about the GPL, please see:
Documentation
-------------
+-------------
The Linux kernel source tree has a large range of documents that are
invaluable for learning how to interact with the kernel community. When
@@ -263,7 +263,7 @@ mailing list about kernel releases:
preconceived timeline."
4.x.y -stable kernel tree
----------------------------
+-------------------------
Kernels with 3-part versions are -stable kernels. They contain
relatively small and critical fixes for security problems or significant
regressions discovered in a given 4.x kernel.
@@ -286,7 +286,7 @@ documents what kinds of changes are acceptable for the -stable tree, and
how the release process works.
4.x -git patches
-------------------
+----------------
These are daily snapshots of Linus' kernel tree which are managed in a
git repository (hence the name.) These patches are usually released
daily and represent the current state of Linus' tree. They are more
@@ -318,7 +318,7 @@ accepted, or rejected. Most of these patchwork sites are listed at
http://patchwork.kernel.org/.
4.x -next kernel tree for integration tests
----------------------------------------------
+-------------------------------------------
Before updates from subsystem trees are merged into the mainline 4.x
tree, they need to be integration-tested. For this purpose, a special
testing repository exists into which virtually all subsystem trees are
--
2.7.2
Powered by blists - more mailing lists