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>,
	LKML <linux-kernel@vger.kernel.org>,
	Jonathan Corbet <corbet@lwn.net>,
	Markus Heiser <markus.heiser@darmarit.de>,
	"David S. Miller" <davem@davemloft.net>,
	Andrew Morton <akpm@linux-foundation.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [PATCH 0/2] Add maintainers to the admin guide
Date: Fri,  2 Dec 2016 10:15:13 -0200	[thread overview]
Message-ID: <cover.1480680547.git.mchehab@s-opensource.com> (raw)

That's my third attempt to add the MAINTAINERS contents to the admin-guide.

On the past approaches, was planning to keep the documentation
about what's at the MAINTAINERS file inside it, but that would
require running an external script or use some Sphinx extension.

This time, I took a much simpler approach: convert the initial
part of the MAINTAINERS file to ReST and move to a file at the
admin-guide. So, MAINTAINERS file will now contain only the
maintainer's database, and a single line pointing to its documentation.

That should hopefully be a good compromise, as we can add its
contents to a Sphinx file without causing too much hasle.


Mauro Carvalho Chehab (2):
  MAINTAINERS: convert first part to ReST markup
  MAINTAINERS: add it to the admin-guide

 Documentation/admin-guide/index.rst       |   1 +
 Documentation/admin-guide/maintainers.rst | 184 ++++++++++++++++++++++++++++++
 MAINTAINERS                               | 125 +-------------------
 3 files changed, 187 insertions(+), 123 deletions(-)
 create mode 100644 Documentation/admin-guide/maintainers.rst

-- 
2.9.3

             reply	other threads:[~2016-12-02 12:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-02 12:15 Mauro Carvalho Chehab [this message]
2016-12-02 12:15 ` [PATCH 1/2] MAINTAINERS: convert first part to ReST markup Mauro Carvalho Chehab
2016-12-02 12:15 ` [PATCH 2/2] MAINTAINERS: add it to the admin-guide Mauro Carvalho Chehab
2016-12-07 15:47 ` [PATCH 0/2] Add maintainers to the admin guide Daniel Vetter
2016-12-12 18:00 ` Jonathan Corbet
2016-12-12 20:56   ` Joe Perches
2016-12-13  9:38     ` Mauro Carvalho Chehab
2016-12-14 16:14       ` Joe Perches
2016-12-14 16:43         ` 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.1480680547.git.mchehab@s-opensource.com \
    --to=mchehab@s-opensource.com \
    --cc=akpm@linux-foundation.org \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=geert+renesas@glider.be \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markus.heiser@darmarit.de \
    --cc=mchehab@infradead.org \
    --cc=mchehab@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