From: Mauro Carvalho Chehab <mchehab@s-opensource.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Jani Nikula <jani.nikula@intel.com>
Subject: Re: [PATCH 08/11] docs: Tweak submitting-patches.rst formatting
Date: Wed, 26 Oct 2016 22:25:41 -0200 [thread overview]
Message-ID: <20161026222541.2cfa65a8@vento.lan> (raw)
In-Reply-To: <1477523979-5837-9-git-send-email-corbet@lwn.net>
Em Wed, 26 Oct 2016 17:19:36 -0600
Jonathan Corbet <corbet@lwn.net> escreveu:
> 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.
>
> Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Looks good to me.
Reviewed-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
> ---
> Documentation/process/submitting-patches.rst | 16 ++++++----------
> 1 file 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>
Thanks,
Mauro
next prev parent reply other threads:[~2016-10-27 0:25 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-26 23:19 [PATCH 00/11] Organize and clean up the admin and process guides Jonathan Corbet
2016-10-26 23:19 ` [PATCH 01/11] docs: Tweak the top-level Sphinx page Jonathan Corbet
2016-10-27 0:12 ` Mauro Carvalho Chehab
2016-10-26 23:19 ` [PATCH 02/11] docs: retitle the kernel-documentation.rst Jonathan Corbet
2016-10-27 0:13 ` Mauro Carvalho Chehab
2016-10-26 23:19 ` [PATCH 03/11] docs: Clean up and organize the admin guide a bit Jonathan Corbet
2016-10-27 0:18 ` Mauro Carvalho Chehab
2016-10-26 23:19 ` [PATCH 04/11] docs: Get rid of the badRAM guide Jonathan Corbet
2016-10-27 0:19 ` Mauro Carvalho Chehab
2016-10-26 23:19 ` [PATCH 05/11] docs: Get rid of the "basic profiling" guide Jonathan Corbet
2016-10-27 0:20 ` Mauro Carvalho Chehab
2016-10-26 23:19 ` [PATCH 06/11] docs: Get rid of the "bug-hunting" guide Jonathan Corbet
2016-10-27 0:23 ` Mauro Carvalho Chehab
2016-10-26 23:19 ` [PATCH 07/11] docs: Apply some basic organization to the process guide Jonathan Corbet
2016-10-27 0:24 ` Mauro Carvalho Chehab
2016-10-26 23:19 ` [PATCH 08/11] docs: Tweak submitting-patches.rst formatting Jonathan Corbet
2016-10-27 0:25 ` Mauro Carvalho Chehab [this message]
2016-10-26 23:19 ` [PATCH 09/11] docs: Collapse the process guide TOC Jonathan Corbet
2016-10-27 0:26 ` Mauro Carvalho Chehab
2016-10-26 23:19 ` [PATCH 10/11] docs: add a warning to submitting-drivers.rst Jonathan Corbet
2016-10-27 0:38 ` Mauro Carvalho Chehab
2016-10-26 23:19 ` [PATCH 11/11] docs: Add a warning to applying-patches.rst Jonathan Corbet
2016-10-27 0:32 ` Mauro Carvalho Chehab
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161026222541.2cfa65a8@vento.lan \
--to=mchehab@s-opensource.com \
--cc=corbet@lwn.net \
--cc=jani.nikula@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome