From: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Viresh Kumar <viresh.kumar@linaro.org>,
Linux PM <linux-pm@vger.kernel.org>
Subject: Re: [PATCH 09/57] docs: cpu-freq: convert files to ReST
Date: Tue, 16 Apr 2019 06:58:15 -0300 [thread overview]
Message-ID: <20190416065815.57fbdf2c@coco.lan> (raw)
In-Reply-To: <CAJZ5v0he8GHZ+EFJ911vgrO53NnEWDwm=_vZD4K9SVL0MahMTQ@mail.gmail.com>
Em Tue, 16 Apr 2019 10:21:31 +0200
"Rafael J. Wysocki" <rafael@kernel.org> escreveu:
> On Tue, Apr 16, 2019 at 4:56 AM Mauro Carvalho Chehab
> <mchehab+samsung@kernel.org> wrote:
> >
> > In order to be able to build html and pdf files, convert the
> > documentation to ReST format.
> >
> > Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
>
> Please don't convert these files.
>
> They need more work than just semi-automatic conversion
Except for one exception (at patch 32/57), the ReST conversion on this
patch set was manually made. I basically renamed the files to
.rst, checked the errors and fixed, trying to preserve the original
document style as much as possible, while providing a good visual
for the html output.
I suspect that trying to write a script for such kind of conversion
is not an easy task, as some documents within the Kernel tree have
their own personal style, (there was even one written in LaTeX at
the CDROM docs), and I suspect that a script would end by adding
extra unwanted markups.
> and the material in them needs to go under driver-api.
Yeah, those documents make sense to be at the driver-api set.
The rationale why I placed the patch with actually renames on a
separate patchset (already on my devel tree, but yet to be submitted)
is that, this way, it should be easy for maintainers to pick the
conversion patch, apply on their trees, and, if they're not ready
yet, postpone the actual rename/move thing.
> This is quite hight in my TODO list.
OK. Feel free to use this patch as a starting point if you
want.
Regards,
Mauro
next prev parent reply other threads:[~2019-04-16 9:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 2:55 [PATCH 00/57] Convert files to ReST Mauro Carvalho Chehab
2019-04-16 2:55 ` Mauro Carvalho Chehab
2019-04-16 2:55 ` [PATCH 09/57] docs: cpu-freq: convert " Mauro Carvalho Chehab
2019-04-16 2:55 ` Mauro Carvalho Chehab
2019-04-16 8:21 ` Rafael J. Wysocki
2019-04-16 8:21 ` Rafael J. Wysocki
2019-04-16 9:58 ` Mauro Carvalho Chehab [this message]
2019-04-16 9:58 ` Mauro Carvalho Chehab
2019-04-16 2:55 ` [PATCH 25/57] docs: power: convert docs " Mauro Carvalho Chehab
2019-04-16 7:20 ` Pavel Machek
2019-04-16 7:20 ` Pavel Machek
2019-04-16 8:59 ` Rafael J. Wysocki
2019-04-16 8:59 ` Rafael J. Wysocki
2019-04-16 10:41 ` Mauro Carvalho Chehab
2019-04-16 10:41 ` Mauro Carvalho Chehab
2019-04-16 10:47 ` Rafael J. Wysocki
2019-04-16 10:47 ` Rafael J. Wysocki
2019-04-18 12:42 ` Avoiding merge conflicts while adding new docs - Was: Re: [PATCH 00/57] Convert files " Mauro Carvalho Chehab
2019-04-18 12:42 ` Mauro Carvalho Chehab
2019-04-19 22:10 ` Jonathan Corbet
2019-04-19 22:10 ` Jonathan Corbet
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=20190416065815.57fbdf2c@coco.lan \
--to=mchehab+samsung@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=viresh.kumar@linaro.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;
as well as URLs for NNTP newsgroup(s).