From: Joe Perches <joe@perches.com>
To: Mauro Carvalho Chehab <mchehab@s-opensource.com>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>
Cc: Mauro Carvalho Chehab <mchehab@infradead.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH v3] docs-rst: user: add MAINTAINERS
Date: Fri, 23 Sep 2016 09:26:34 -0700 [thread overview]
Message-ID: <1474647994.1849.1.camel@perches.com> (raw)
In-Reply-To: <20160923120733.546a4b7a@vento.lan>
On Fri, 2016-09-23 at 12:07 -0300, Mauro Carvalho Chehab wrote:
> So, let's use an unusual approach: manually convert the
> text at the MAINTAINERS file head, adding it at a new
> Documentation/user/MAINTAINERS.rst, and include, as a code
> block, the rest of MAINTAINERS contents, with only the
> contents of the maintainers entries.
>
> There's a side effect of this approach: now, if the
> explanation text at the MAINTAINERS file is touched, it should be
> modified also at the Documentation/user/MAINTAINERS.rst file.
> Yet, as the number of changes there are small, this
> should be manageable.
couldn't this be a generated file from some awk script instead
of being duplicated content with a plea to be kept in sync?
> diff --git a/Documentation/user/MAINTAINERS.rst b/Documentation/user/MAINTAINERS.rst
> new file mode 100644
[etc]
next prev parent reply other threads:[~2016-09-23 16:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-23 15:07 [RFC PATCH v3] docs-rst: user: add MAINTAINERS Mauro Carvalho Chehab
2016-09-23 15:15 ` Jonathan Corbet
2016-09-23 15:35 ` Mauro Carvalho Chehab
2016-09-23 16:26 ` Markus Heiser
2016-09-23 16:26 ` Joe Perches [this message]
2016-09-23 17:50 ` 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=1474647994.1849.1.camel@perches.com \
--to=joe@perches.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=mchehab@kernel.org \
--cc=mchehab@s-opensource.com \
/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;
as well as URLs for NNTP newsgroup(s).