summaryrefslogtreecommitdiffstats
path: root/Documentation/process/howto.rst
diff options
context:
space:
mode:
authorSeongJae Park <sj38.park@gmail.com>2016-10-31 16:27:10 -0400
committerJonathan Corbet <corbet@lwn.net>2016-11-07 19:03:50 -0500
commitd80b9d2aba35d2c9c030c77ad463454c077959ea (patch)
tree17318909752a84e8b9153d361fe4479d4fe530db /Documentation/process/howto.rst
parentf226e460875da8e00febf55e5ec3438e498ca676 (diff)
Documentation/process/howto: Mark subsection in suggested format
`Specific guidelines for the kernel documentation` section of `kernel-documentation.rst` suggests to use ``~`` for subsection but subsections in HOWTO is not marked in the format. This commit marks them in the format. Signed-off-by: SeongJae Park <sj38.park@gmail.com> Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Diffstat (limited to 'Documentation/process/howto.rst')
-rw-r--r--Documentation/process/howto.rst15
1 files changed, 10 insertions, 5 deletions
diff --git a/Documentation/process/howto.rst b/Documentation/process/howto.rst
index 3f66a1980726..449ca1f199f4 100644
--- a/Documentation/process/howto.rst
+++ b/Documentation/process/howto.rst
@@ -254,7 +254,8 @@ branches. These different branches are:
254 - the 4.x -next kernel tree for integration tests 254 - the 4.x -next kernel tree for integration tests
255 255
2564.x kernel tree 2564.x kernel tree
257----------------- 257~~~~~~~~~~~~~~~
258
2584.x kernels are maintained by Linus Torvalds, and can be found on 2594.x kernels are maintained by Linus Torvalds, and can be found on
259https://kernel.org in the pub/linux/kernel/v4.x/ directory. Its development 260https://kernel.org in the pub/linux/kernel/v4.x/ directory. Its development
260process is as follows: 261process is as follows:
@@ -289,7 +290,8 @@ mailing list about kernel releases:
289 preconceived timeline."* 290 preconceived timeline."*
290 291
2914.x.y -stable kernel tree 2924.x.y -stable kernel tree
292------------------------- 293~~~~~~~~~~~~~~~~~~~~~~~~~
294
293Kernels with 3-part versions are -stable kernels. They contain 295Kernels with 3-part versions are -stable kernels. They contain
294relatively small and critical fixes for security problems or significant 296relatively small and critical fixes for security problems or significant
295regressions discovered in a given 4.x kernel. 297regressions discovered in a given 4.x kernel.
@@ -312,7 +314,8 @@ documents what kinds of changes are acceptable for the -stable tree, and
312how the release process works. 314how the release process works.
313 315
3144.x -git patches 3164.x -git patches
315---------------- 317~~~~~~~~~~~~~~~~
318
316These are daily snapshots of Linus' kernel tree which are managed in a 319These are daily snapshots of Linus' kernel tree which are managed in a
317git repository (hence the name.) These patches are usually released 320git repository (hence the name.) These patches are usually released
318daily and represent the current state of Linus' tree. They are more 321daily and represent the current state of Linus' tree. They are more
@@ -320,7 +323,8 @@ experimental than -rc kernels since they are generated automatically
320without even a cursory glance to see if they are sane. 323without even a cursory glance to see if they are sane.
321 324
322Subsystem Specific kernel trees and patches 325Subsystem Specific kernel trees and patches
323------------------------------------------- 326~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
327
324The maintainers of the various kernel subsystems --- and also many 328The maintainers of the various kernel subsystems --- and also many
325kernel subsystem developers --- expose their current state of 329kernel subsystem developers --- expose their current state of
326development in source repositories. That way, others can see what is 330development in source repositories. That way, others can see what is
@@ -344,7 +348,8 @@ accepted, or rejected. Most of these patchwork sites are listed at
344https://patchwork.kernel.org/. 348https://patchwork.kernel.org/.
345 349
3464.x -next kernel tree for integration tests 3504.x -next kernel tree for integration tests
347------------------------------------------- 351~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
352
348Before updates from subsystem trees are merged into the mainline 4.x 353Before updates from subsystem trees are merged into the mainline 4.x
349tree, they need to be integration-tested. For this purpose, a special 354tree, they need to be integration-tested. For this purpose, a special
350testing repository exists into which virtually all subsystem trees are 355testing repository exists into which virtually all subsystem trees are