linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
Cc: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
	Mauro Carvalho Chehab <mchehab@infradead.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 00/10] Add all documentation files to an html/pdf produced book
Date: Thu, 11 Apr 2019 12:49:04 -0600	[thread overview]
Message-ID: <20190411124904.12e61bc7@lwn.net> (raw)
In-Reply-To: <20190410064939.2a9dca9a@coco.lan>

On Wed, 10 Apr 2019 06:49:39 -0300
Mauro Carvalho Chehab <mchehab+samsung@kernel.org> wrote:

[I'm just responding to one little piece of this for the moment...]

> In any case, IMHO, the best would be to add a new
> crap^h^h^h^hstaging group were we could place all legacy random stuff.
> Then, gradually fix those, splitting stuff and promoting them to the
> main books, in a similar way to what we do with staging.

Now that's an interesting idea; I hadn't thought about that.  Doing so,
though, implies a willingness to stage unloved docs *out*, and my
experience is that there is little appetite for that.  It also kind of
implies moving docs twice - at least for the ones that get updates - and
that may not be entirely appreciated.

> > I feel like it would, if anything, reduce the incentive to
> > deal with these leftover documents properly.    
> 
> IMHO, it is just the opposite. Let's face it: ReST build was added around
> May, 2016, for Kernel 4.7. People had quite some time and kernel versions
> to do conversions. If nothing is done, I doubt we would have any boom on
> patches addressing the issues.

So I don't have any hard numbers, but my feeling is that this work is
continuing apace and perhaps even picking up.  Certainly I'm having a
harder time keeping up with it, even when you're busy with other things :)
These things take time; I'm not really ready to give up on it yet.

Thanks,

jon

  reply	other threads:[~2019-04-11 18:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-08 16:58 [PATCH 00/10] Add all documentation files to an html/pdf produced book Mauro Carvalho Chehab
2019-04-08 16:58 ` [PATCH 01/10] docs: DMA-API-HOWTO: add a missing "=" Mauro Carvalho Chehab
2019-04-08 16:58 ` [PATCH 02/10] docs: atomic_bitops.txt: add a title for this document Mauro Carvalho Chehab
2019-04-08 16:58 ` [PATCH 03/10] docs: clearing-warn-once.txt: " Mauro Carvalho Chehab
2019-04-08 16:58 ` [PATCH 04/10] docs: ntb.txt: use Sphinx notation for the two ascii figures Mauro Carvalho Chehab
2019-04-08 16:58 ` [PATCH 05/10] docs: unaligned-memory-access.txt: use a lowercase title Mauro Carvalho Chehab
2019-04-08 16:58 ` [PATCH 06/10] docs: video-output.txt: convert it to ReST format Mauro Carvalho Chehab
2019-04-08 16:58 ` [PATCH 07/10] docs: Add all txt files to documentation Mauro Carvalho Chehab
2019-04-09 16:47   ` Joe Perches
2019-04-08 16:58 ` [PATCH 08/10] docs: ntb.rst: add blank lines to clean up some Sphinx warnings Mauro Carvalho Chehab
2019-04-08 16:58 ` [PATCH 09/10] docs: speculation.rst: mark example blocks as such Mauro Carvalho Chehab
2019-04-08 16:58 ` [PATCH 10/10] docs: add plain text files to ReST output from subdirs Mauro Carvalho Chehab
2019-04-08 22:18 ` [PATCH 00/10] Add all documentation files to an html/pdf produced book Jonathan Corbet
2019-04-10  9:49   ` Mauro Carvalho Chehab
2019-04-11 18:49     ` Jonathan Corbet [this message]
2019-04-12  9:28       ` Mauro Carvalho Chehab
2019-04-13  0:30         ` 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=20190411124904.12e61bc7@lwn.net \
    --to=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab+samsung@kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).