summaryrefslogtreecommitdiffstats
path: root/Documentation/development-process/8.Conclusion
diff options
context:
space:
mode:
authorMauro Carvalho Chehab <mchehab@s-opensource.com>2016-09-19 08:07:37 -0300
committerJonathan Corbet <corbet@lwn.net>2016-09-20 18:31:29 -0600
commit88b72c08e852d08c3f7761805a3a919935b64e22 (patch)
tree47f8eaa7c8ce98caec5a40be6fae9ac4710bf0fc /Documentation/development-process/8.Conclusion
parentf7c9fe4b1cd144f7afc1712bb25141c55c406e1b (diff)
downloadlinux-88b72c08e852d08c3f7761805a3a919935b64e22.tar.gz
linux-88b72c08e852d08c3f7761805a3a919935b64e22.tar.bz2
linux-88b72c08e852d08c3f7761805a3a919935b64e22.zip
doc: development-process: rename files to rst
Now that the documents were converted, rename them to .rst, as this is needed by the Sphinx build logic. Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com> Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Diffstat (limited to 'Documentation/development-process/8.Conclusion')
-rw-r--r--Documentation/development-process/8.Conclusion74
1 files changed, 0 insertions, 74 deletions
diff --git a/Documentation/development-process/8.Conclusion b/Documentation/development-process/8.Conclusion
deleted file mode 100644
index 23ec7cbc2d2b..000000000000
--- a/Documentation/development-process/8.Conclusion
+++ /dev/null
@@ -1,74 +0,0 @@
-.. _development_conclusion:
-
-For more information
-====================
-
-There are numerous sources of information on Linux kernel development and
-related topics. First among those will always be the Documentation
-directory found in the kernel source distribution. The top-level HOWTO
-file is an important starting point; SubmittingPatches and
-SubmittingDrivers are also something which all kernel developers should
-read. Many internal kernel APIs are documented using the kerneldoc
-mechanism; "make htmldocs" or "make pdfdocs" can be used to generate those
-documents in HTML or PDF format (though the version of TeX shipped by some
-distributions runs into internal limits and fails to process the documents
-properly).
-
-Various web sites discuss kernel development at all levels of detail. Your
-author would like to humbly suggest http://lwn.net/ as a source;
-information on many specific kernel topics can be found via the LWN kernel
-index at:
-
- http://lwn.net/Kernel/Index/
-
-Beyond that, a valuable resource for kernel developers is:
-
- http://kernelnewbies.org/
-
-And, of course, one should not forget http://kernel.org/, the definitive
-location for kernel release information.
-
-There are a number of books on kernel development:
-
- Linux Device Drivers, 3rd Edition (Jonathan Corbet, Alessandro
- Rubini, and Greg Kroah-Hartman). Online at
- http://lwn.net/Kernel/LDD3/.
-
- Linux Kernel Development (Robert Love).
-
- Understanding the Linux Kernel (Daniel Bovet and Marco Cesati).
-
-All of these books suffer from a common fault, though: they tend to be
-somewhat obsolete by the time they hit the shelves, and they have been on
-the shelves for a while now. Still, there is quite a bit of good
-information to be found there.
-
-Documentation for git can be found at:
-
- http://www.kernel.org/pub/software/scm/git/docs/
-
- http://www.kernel.org/pub/software/scm/git/docs/user-manual.html
-
-
-Conclusion
-==========
-
-Congratulations to anybody who has made it through this long-winded
-document. Hopefully it has provided a helpful understanding of how the
-Linux kernel is developed and how you can participate in that process.
-
-In the end, it's the participation that matters. Any open source software
-project is no more than the sum of what its contributors put into it. The
-Linux kernel has progressed as quickly and as well as it has because it has
-been helped by an impressively large group of developers, all of whom are
-working to make it better. The kernel is a premier example of what can be
-done when thousands of people work together toward a common goal.
-
-The kernel can always benefit from a larger developer base, though. There
-is always more work to do. But, just as importantly, most other
-participants in the Linux ecosystem can benefit through contributing to the
-kernel. Getting code into the mainline is the key to higher code quality,
-lower maintenance and distribution costs, a higher level of influence over
-the direction of kernel development, and more. It is a situation where
-everybody involved wins. Fire up your editor and come join us; you will be
-more than welcome.