diff options
| author | Mauro Carvalho Chehab <mchehab@s-opensource.com> | 2016-09-19 08:07:36 -0300 |
|---|---|---|
| committer | Jonathan Corbet <corbet@lwn.net> | 2016-09-20 18:30:43 -0600 |
| commit | f7c9fe4b1cd144f7afc1712bb25141c55c406e1b (patch) | |
| tree | ad56ecfa99ef9abe7dd84744cf7dc3770bf1d087 /Documentation/development-process/7.AdvancedTopics | |
| parent | 1414f0488803d8963b5868b1512515c997b54571 (diff) | |
| download | blackbird-op-linux-f7c9fe4b1cd144f7afc1712bb25141c55c406e1b.tar.gz blackbird-op-linux-f7c9fe4b1cd144f7afc1712bb25141c55c406e1b.zip | |
doc: development-process: convert it to ReST markup
This document is on good shape for ReST: all it was needed was
to fix the section markups, add a toctree, convert the tables
and add a few code/quote blocks.
While not strictly required, I opted to use lowercase for
the titles, just like the other books that were converted
to Sphinx.
Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
Diffstat (limited to 'Documentation/development-process/7.AdvancedTopics')
| -rw-r--r-- | Documentation/development-process/7.AdvancedTopics | 13 |
1 files changed, 10 insertions, 3 deletions
diff --git a/Documentation/development-process/7.AdvancedTopics b/Documentation/development-process/7.AdvancedTopics index 26dc3fa196e4..81d61c5d62dd 100644 --- a/Documentation/development-process/7.AdvancedTopics +++ b/Documentation/development-process/7.AdvancedTopics @@ -1,11 +1,15 @@ -7: ADVANCED TOPICS +.. _development_advancedtopics: + +Advanced topics +=============== At this point, hopefully, you have a handle on how the development process works. There is still more to learn, however! This section will cover a number of topics which can be helpful for developers wanting to become a regular part of the Linux kernel development process. -7.1: MANAGING PATCHES WITH GIT +Managing patches with git +------------------------- The use of distributed version control for the kernel began in early 2002, when Linus first started playing with the proprietary BitKeeper @@ -114,6 +118,8 @@ radar. Kernel developers tend to get unhappy when they see that kind of thing happening; putting up a git tree with unreviewed or off-topic patches can affect your ability to get trees pulled in the future. Quoting Linus: +:: + You can send me patches, but for me to pull a git patch from you, I need to know that you know what you're doing, and I need to be able to trust things *without* then having to go and check every @@ -141,7 +147,8 @@ format the request as other developers expect, and will also check to be sure that you have remembered to push those changes to the public server. -7.2: REVIEWING PATCHES +Reviewing patches +----------------- Some readers will certainly object to putting this section with "advanced topics" on the grounds that even beginning kernel developers should be |
