diff options
| author | Jonathan Corbet <corbet@lwn.net> | 2016-10-26 16:37:53 -0600 |
|---|---|---|
| committer | Jonathan Corbet <corbet@lwn.net> | 2016-10-27 16:37:35 -0600 |
| commit | 89edeedd61e8faa4e092f3797606739317abeb6c (patch) | |
| tree | bb5b4d150e7b6853ab62c2666fd3ee023bb1742a /Documentation/process | |
| parent | 9b4ebd98da9112f974a6db58555a33eb1bd7c0b0 (diff) | |
| download | linux-89edeedd61e8faa4e092f3797606739317abeb6c.tar.gz linux-89edeedd61e8faa4e092f3797606739317abeb6c.tar.bz2 linux-89edeedd61e8faa4e092f3797606739317abeb6c.zip | |
docs: Tweak submitting-patches.rst formatting
The main goal here was to get the subsections to show in the TOC as they do
for all the other documents. Also call out the DCO in the section title
since it's important.
Reviewed-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Diffstat (limited to 'Documentation/process')
| -rw-r--r-- | Documentation/process/submitting-patches.rst | 16 |
1 files changed, 6 insertions, 10 deletions
diff --git a/Documentation/process/submitting-patches.rst b/Documentation/process/submitting-patches.rst index b4cf8f375184..3e10719fee35 100644 --- a/Documentation/process/submitting-patches.rst +++ b/Documentation/process/submitting-patches.rst @@ -1,7 +1,7 @@ .. _submittingpatches: -How to Get Your Change Into the Linux Kernel or Care And Operation Of Your Linus Torvalds -========================================================================================= +Submitting patches: the essential guide to getting your code into the kernel +============================================================================ For a person or company who wishes to submit a change to the Linux kernel, the process can sometimes be daunting if you're not familiar @@ -24,10 +24,6 @@ of the mechanical work done for you, though you'll still need to prepare and document a sensible set of patches. In general, use of ``git`` will make your life as a kernel developer easier. -Creating and Sending your Change -******************************** - - 0) Obtain a current source tree ------------------------------- @@ -417,8 +413,8 @@ e-mail discussions. -11) Sign your work ------------------- +11) Sign your work — the Developer's Certificate of Origin +---------------------------------------------------------- To improve tracking of who did what, especially with patches that can percolate to their final resting place in the kernel through several @@ -803,8 +799,8 @@ command like this will do the trick:: git request-pull master git://my.public.tree/linux.git my-signed-tag -REFERENCES -********** +References +---------- Andrew Morton, "The perfect patch" (tpp). <http://www.ozlabs.org/~akpm/stuff/tpp.txt> |