public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@s-opensource.com>
To: Linux Doc Mailing List <linux-doc@vger.kernel.org>
Cc: Mauro Carvalho Chehab <mchehab@s-opensource.com>,
	Mauro Carvalho Chehab <mchehab@infradead.org>,
	Markus Heiser <markus.heiser@darmarit.de>,
	Jonathan Corbet <corbet@lwn.net>,
	Jani Nikula <jani.nikula@linux.intel.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH 00/17] Improve documentation for the development-process
Date: Wed, 14 Sep 2016 20:05:45 -0300	[thread overview]
Message-ID: <cover.1473893776.git.mchehab@s-opensource.com> (raw)

This patch series is a followup to be applied after the:
	[PATCH v3 00/21] Create a book for Kernel development

patch series.

It addresses some issues I noticed after re-reading the html docs 
after the conversion of those files to ReST.

It also converts two extra documents to ReST:
   Documentation/SubmitChecklist
   Documentation/email-clients.txt

Both are mentioned on the previous document, and are part of the
patch submission process. So, it makes sense to group them at the
development-process book.

I also took the time to update the applying-patches.rst, as I found some
outdated information there.

Regards,
Mauro

Mauro Carvalho Chehab (17):
  HOWTO.rst: update information about generating documentation
  HOWTO.rst: improve some markups to make it visually better
  HOWTO.rst: adjust external link references
  Changes.rst: add minimal requirements for documentation build
  SubmitChecklist: update kernel-doc task
  SubmitChecklist: convert it to ReST markup
  SubmitChecklist: rename to RST and add to the development-proccess
    book
  doc-rst: add CSS styles for :kbd: and :menuselection:
  email-clients.txt: convert it to ReST markup
  email-clients.txt: add it to the development-process book
  SubmittingPatches.rst: Add some cross-references
  SubmittingPatches.rst: enrich the Sphinx output
  SubmittingDrivers.rst: add a cross reference to CodingStyle
  stable_api_nonsense.rst: fix emphasis on Sphinx
  ManagementStyle.rst: avoid emphasis where not desired
  stable_kernel_rules.rst: Add cross-references to other ReST files
  applying-patches.rst: Update the information there

 Documentation/SubmitChecklist                      | 109 ---------
 Documentation/development-process/5.Posting.rst    |   2 +-
 Documentation/development-process/Changes.rst      |  36 ++-
 Documentation/development-process/HOWTO.rst        | 101 ++++----
 .../development-process/ManagementStyle.rst        |   2 +
 .../development-process/SubmitChecklist.rst        | 120 ++++++++++
 .../development-process/SubmittingDrivers.rst      |   7 +-
 .../development-process/SubmittingPatches.rst      | 124 +++++-----
 .../development-process/applying-patches.rst       | 255 +++++++++------------
 .../development-process/development-process.rst    |   2 +
 .../email-clients.rst}                             | 216 +++++++++--------
 Documentation/development-process/index.rst        |   2 +
 .../development-process/stable_api_nonsense.rst    |   2 +-
 .../development-process/stable_kernel_rules.rst    |   7 +-
 Documentation/hwmon/submitting-patches             |   2 +-
 Documentation/ja_JP/SubmitChecklist                |   4 +-
 Documentation/ja_JP/SubmittingPatches              |   4 +-
 Documentation/kernel-documentation.rst             |   2 +
 Documentation/sphinx-static/theme_overrides.css    |  15 +-
 Documentation/zh_CN/SubmittingPatches              |   2 +-
 Documentation/zh_CN/email-clients.txt              |   4 +-
 21 files changed, 555 insertions(+), 463 deletions(-)
 delete mode 100644 Documentation/SubmitChecklist
 create mode 100644 Documentation/development-process/SubmitChecklist.rst
 rename Documentation/{email-clients.txt => development-process/email-clients.rst} (56%)

-- 
2.7.4

             reply	other threads:[~2016-09-14 23:09 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-14 23:05 Mauro Carvalho Chehab [this message]
2016-09-14 23:05 ` [PATCH 01/17] HOWTO.rst: update information about generating documentation Mauro Carvalho Chehab
2016-09-14 23:05 ` [PATCH 02/17] HOWTO.rst: improve some markups to make it visually better Mauro Carvalho Chehab
2016-09-14 23:05 ` [PATCH 03/17] HOWTO.rst: adjust external link references Mauro Carvalho Chehab
2016-09-14 23:05 ` [PATCH 04/17] Changes.rst: add minimal requirements for documentation build Mauro Carvalho Chehab
2016-09-14 23:05 ` [PATCH 05/17] SubmitChecklist: update kernel-doc task Mauro Carvalho Chehab
2016-09-14 23:05 ` [PATCH 06/17] SubmitChecklist: convert it to ReST markup Mauro Carvalho Chehab
2016-09-14 23:05 ` [PATCH 07/17] SubmitChecklist: rename to RST and add to the development-proccess book Mauro Carvalho Chehab
2016-09-16  8:11   ` Jean Delvare
2016-09-14 23:05 ` [PATCH 08/17] doc-rst: add CSS styles for :kbd: and :menuselection: Mauro Carvalho Chehab
2016-09-14 23:05 ` [PATCH 09/17] email-clients.txt: convert it to ReST markup Mauro Carvalho Chehab
2016-09-14 23:05 ` [PATCH 10/17] email-clients.txt: add it to the development-process book Mauro Carvalho Chehab
2016-09-14 23:05 ` [PATCH 11/17] SubmittingPatches.rst: Add some cross-references Mauro Carvalho Chehab
2016-09-14 23:05 ` [PATCH 12/17] SubmittingPatches.rst: enrich the Sphinx output Mauro Carvalho Chehab
2016-09-14 23:05 ` [PATCH 13/17] SubmittingDrivers.rst: add a cross reference to CodingStyle Mauro Carvalho Chehab
2016-09-14 23:05 ` [PATCH 14/17] stable_api_nonsense.rst: fix emphasis on Sphinx Mauro Carvalho Chehab
2016-09-14 23:06 ` [PATCH 15/17] ManagementStyle.rst: avoid emphasis where not desired Mauro Carvalho Chehab
2016-09-14 23:06 ` [PATCH 16/17] stable_kernel_rules.rst: Add cross-references to other ReST files Mauro Carvalho Chehab
2016-09-14 23:06 ` [PATCH 17/17] applying-patches.rst: Update the information there 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=cover.1473893776.git.mchehab@s-opensource.com \
    --to=mchehab@s-opensource.com \
    --cc=corbet@lwn.net \
    --cc=jani.nikula@linux.intel.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markus.heiser@darmarit.de \
    --cc=mchehab@infradead.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