diff options
| author | Mauro Carvalho Chehab <mchehab@s-opensource.com> | 2016-09-19 14:07:36 +0300 |
|---|---|---|
| committer | Jonathan Corbet <corbet@lwn.net> | 2016-09-21 03:30:43 +0300 |
| commit | f7c9fe4b1cd144f7afc1712bb25141c55c406e1b (patch) | |
| tree | ad56ecfa99ef9abe7dd84744cf7dc3770bf1d087 /Documentation/development-process/6.Followthrough | |
| parent | 1414f0488803d8963b5868b1512515c997b54571 (diff) | |
| download | linux-f7c9fe4b1cd144f7afc1712bb25141c55c406e1b.tar.xz | |
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/6.Followthrough')
| -rw-r--r-- | Documentation/development-process/6.Followthrough | 14 |
1 files changed, 10 insertions, 4 deletions
diff --git a/Documentation/development-process/6.Followthrough b/Documentation/development-process/6.Followthrough index 41d324a9420d..a173cd5f93d2 100644 --- a/Documentation/development-process/6.Followthrough +++ b/Documentation/development-process/6.Followthrough @@ -1,4 +1,7 @@ -6: FOLLOWTHROUGH +.. _development_followthrough: + +Followthrough +============= At this point, you have followed the guidelines given so far and, with the addition of your own engineering skills, have posted a perfect series of @@ -16,7 +19,8 @@ standards. A failure to participate in this process is quite likely to prevent the inclusion of your patches into the mainline. -6.1: WORKING WITH REVIEWERS +Working with reviewers +---------------------- A patch of any significance will result in a number of comments from other developers as they review the code. Working with reviewers can be, for @@ -97,7 +101,8 @@ though, and not before all other alternatives have been explored. And bear in mind, of course, that he may not agree with you either. -6.2: WHAT HAPPENS NEXT +What happens next +----------------- If a patch is considered to be a good thing to add to the kernel, and once most of the review issues have been resolved, the next step is usually @@ -177,7 +182,8 @@ it with the assumption that you will not be around to maintain it afterward. -6.3: OTHER THINGS THAT CAN HAPPEN +Other things that can happen +----------------------------- One day, you may open your mail client and see that somebody has mailed you a patch to your code. That is one of the advantages of having your code |