diff options
| author | Jonathan Corbet <corbet@lwn.net> | 2016-10-28 02:05:10 +0300 |
|---|---|---|
| committer | Jonathan Corbet <corbet@lwn.net> | 2016-10-28 02:47:58 +0300 |
| commit | 9d2cccdd6c226181c42a7bb0c5ede1583687b618 (patch) | |
| tree | 993ff17c35fd23a71533e63f6943b9bf59e1d5e4 /Documentation/process/submitting-patches.rst | |
| parent | 2797cd03f5cca4d9fb2875c9f9c995737ce73469 (diff) | |
| parent | 67972a539e9ff1a3ed794c463c4e544442df693e (diff) | |
| download | linux-9d2cccdd6c226181c42a7bb0c5ede1583687b618.tar.xz | |
Merge branch 'doc-tweaks' into docs-next
The creation of the admin and process guides is a great thing, but, without
care, we risk replacing a messy docs directory with a few messy Sphinx
books. In an attempt to head that off and show what I'm thinking, here's a
set of tweaks that, I think, make the existing Sphinx-formatted docs a bit
more accessible.
Diffstat (limited to 'Documentation/process/submitting-patches.rst')
| -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> |