2b7703e15a
The canonical way to add a heading to the ToC is to use :caption:. Do that. Let's also move the introduction to the top of the document to be consistent with most other documents. Cc: Jonathan Corbet <corbet@lwn.net> Cc: Mauro Carvalho Chehab <mchehab@kernel.org> Cc: Federico Vaga <federico.vaga@vaga.pv.it> Cc: Alex Shi <alexs@kernel.org> Cc: Yanteng Si <siyanteng@loongson.cn> Cc: Hu Haowen <src.res.211@gmail.com> Cc: workflows@vger.kernel.org Signed-off-by: Vegard Nossum <vegard.nossum@oracle.com> Signed-off-by: Jonathan Corbet <corbet@lwn.net> Link: https://lore.kernel.org/r/20231027081830.195056-11-vegard.nossum@oracle.com
28 lines
821 B
ReStructuredText
28 lines
821 B
ReStructuredText
.. _development_process_main:
|
|
|
|
A guide to the Kernel Development Process
|
|
=========================================
|
|
|
|
The purpose of this document is to help developers (and their managers)
|
|
work with the development community with a minimum of frustration. It is
|
|
an attempt to document how this community works in a way which is
|
|
accessible to those who are not intimately familiar with Linux kernel
|
|
development (or, indeed, free software development in general). While
|
|
there is some technical material here, this is very much a process-oriented
|
|
discussion which does not require a deep knowledge of kernel programming to
|
|
understand.
|
|
|
|
.. toctree::
|
|
:caption: Contents
|
|
:numbered:
|
|
:maxdepth: 2
|
|
|
|
1.Intro
|
|
2.Process
|
|
3.Early-stage
|
|
4.Coding
|
|
5.Posting
|
|
6.Followthrough
|
|
7.AdvancedTopics
|
|
8.Conclusion
|