Linux Device Mapper development
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Mike Snitzer <snitzer@redhat.com>,
	Linux Doc Mailing List <linux-doc@vger.kernel.org>,
	Mauro Carvalho Chehab <mchehab@infradead.org>,
	linux-kernel@vger.kernel.org, Alasdair Kergon <agk@redhat.com>,
	dm-devel@redhat.com
Subject: Re: [PATCH 10/57] docs: device-mapper: convert it to ReST format
Date: Tue, 16 Apr 2019 11:33:16 -0300	[thread overview]
Message-ID: <20190416113316.5c3b496c@coco.lan> (raw)
In-Reply-To: <20190416080024.7fb65682@lwn.net>

Em Tue, 16 Apr 2019 08:00:24 -0600
Jonathan Corbet <corbet@lwn.net> escreveu:

> On Tue, 16 Apr 2019 09:28:52 -0400
> Mike Snitzer <snitzer@redhat.com> wrote:
> 
> > Can you help me understand why this is the direction text based
> > Documenation is taking in the Linux kernel?  All I see is markup, and
> > escaping of characters, that is a chore to administer over time.  
> 
> This is a discussion that was mostly resolved some years ago...
> 
> Classic Documentation/ is a jumbled collection of unorganized text files,
> some of which contain highly useful information and others of which
> haven't had much to offer since about 1996.  We are working to turn it
> into an organized collection where, hopefully, some thought has actually
> been given to the people who will be reading it.
> 
> The ReST conversion, in particular, allows us to link documents into a
> larger structure, create indexes and cross references, and produce output
> in formats like HTML and PDF.  It lets us present the documentation like
> this:
> 
> 	https://www.kernel.org/doc/html/latest/

Just to mention, in the specific case of the device-mapper patch,
this is the result of those changes (after renaming the files to .rst,
and adding an index file):

	https://www.infradead.org/~mchehab/rst_conversion/device-mapper/index.html

> 
> Among other things, making the documentation more accessible in this way
> makes it easier and more rewarding for developers to improve it, and I
> believe we are seeing the results of that.  Linus called out the
> documentation work in the 5.1-rc1 announcement, for example.
> 
> Nobody has complained about the maintenance burden of RST docs - so far as
> I have heard, anyway.  Things do break occasionally, but problems in the
> docs build almost always result from code changes that mess up the
> kerneldoc comments rather than RST changes, and it's been that way for as
> long as I've been paying attention.


> 
> Thanks,
> 
> jon



Thanks,
Mauro

  reply	other threads:[~2019-04-16 14:33 UTC|newest]

Thread overview: 10+ 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 ` [PATCH 10/57] docs: device-mapper: convert it to ReST format Mauro Carvalho Chehab
2019-04-16 13:28   ` Mike Snitzer
2019-04-16 14:00     ` Jonathan Corbet
2019-04-16 14:33       ` Mauro Carvalho Chehab [this message]
2019-04-16 15:48       ` Mike Snitzer
2019-04-16 17:27         ` Jonathan Corbet
2019-04-16 18:14         ` Mauro Carvalho Chehab
2019-04-18 12:42 ` Avoiding merge conflicts while adding new docs - Was: Re: [PATCH 00/57] Convert files to ReST Mauro Carvalho Chehab
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=20190416113316.5c3b496c@coco.lan \
    --to=mchehab+samsung@kernel.org \
    --cc=agk@redhat.com \
    --cc=corbet@lwn.net \
    --cc=dm-devel@redhat.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@infradead.org \
    --cc=snitzer@redhat.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