All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Jani Nikula <jani.nikula@intel.com>
Cc: Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
	Markus Heiser <markus.heiser@darmarit.de>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	hverkuil@xs4all.nl, daniel.vetter@ffwll.ch, airlied@gmail.com,
	grant.likely@secretlab.ca, rdunlap@infradead.org,
	keithp@keithp.com
Subject: Re: [PATCH] doc: flat-table directive
Date: Fri, 1 Jul 2016 06:58:21 -0600	[thread overview]
Message-ID: <20160701065821.59196b28@lwn.net> (raw)
In-Reply-To: <87shvtpri6.fsf@intel.com>

On Fri, 01 Jul 2016 13:44:17 +0300
Jani Nikula <jani.nikula@intel.com> wrote:

> This is also one of the reasons why I so much want to keep everything
> behind one configuration file, and build everything in the Sphinx
> toolchain. To keep it all more uniform, to not duplicate stuff, and not
> deviate to some silos like we've done in the past. I think when we have
> things working, we can add dedicated config files for the select few
> things that have additional special needs. Media is probably one of
> them. But that said, I think we should be able to keep including that to
> the main documentation build too.

So this is mostly how I see things too.  But it might still be worth
thinking about whether media, in particular, is special and should be
buildable as a standalone document.  I can see there may be settings
where only that is wanted.

Some sort of "only build xxx.rst and see what explodes" makefile option
also seems like a useful thing to have, just as a time saver for
developers and maintainers.

jon

  parent reply	other threads:[~2016-07-01 13:28 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-30 12:00 [PATCH] doc: flat-table directive Markus Heiser
2016-06-30 12:00 ` [PATCH] doc-rst: flat-table directive - initial implementation Markus Heiser
2016-06-30 19:05 ` [PATCH] doc: flat-table directive Jonathan Corbet
2016-06-30 19:31   ` Mauro Carvalho Chehab
2016-06-30 19:44   ` Mauro Carvalho Chehab
2016-07-01  8:44     ` Markus Heiser
2016-07-01  9:38       ` Mauro Carvalho Chehab
2016-07-01 10:44         ` Jani Nikula
2016-07-01 11:12           ` Markus Heiser
2016-07-01 11:56             ` Jani Nikula
2016-07-01 12:03               ` [docs-next PATCH] Documentation: add cleanmediadocs to the documentation targets Jani Nikula
2016-07-01 12:24                 ` [docs-next PATCH] Documentation/sphinx: skip build if user requested specific DOCBOOKS Jani Nikula
2016-07-01 12:31                   ` Markus Heiser
2016-07-01 13:15                   ` Mauro Carvalho Chehab
2016-07-01 13:31                     ` Jani Nikula
2016-07-01 15:09                       ` Mauro Carvalho Chehab
2016-07-01 12:04               ` [PATCH] doc: flat-table directive Markus Heiser
2016-07-01 12:26                 ` Jani Nikula
2016-07-01 13:06                   ` Mauro Carvalho Chehab
2016-07-01 12:52           ` Mauro Carvalho Chehab
2016-07-01 12:58           ` Jonathan Corbet [this message]
2016-07-01 14:45             ` Markus Heiser
2016-07-01 17:24               ` Jani Nikula
2016-07-01 18:17                 ` Mauro Carvalho Chehab
2016-07-01 18:47                   ` Jani Nikula
2016-07-01 12:18         ` Markus Heiser
2016-07-01 12:59           ` Mauro Carvalho Chehab
2016-07-01 13:09           ` Jani Nikula
2016-07-01 14:07             ` Markus Heiser
2016-07-01 15:00               ` Mauro Carvalho Chehab
2016-07-01 15:01               ` Mauro Carvalho Chehab
2016-07-06 22:58               ` Mauro Carvalho Chehab
2016-07-01 12:08     ` Jani Nikula
2016-07-01  6:35   ` Markus Heiser
2016-07-01 18:25 ` Captions numbering support 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=20160701065821.59196b28@lwn.net \
    --to=corbet@lwn.net \
    --cc=airlied@gmail.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=grant.likely@secretlab.ca \
    --cc=hverkuil@xs4all.nl \
    --cc=jani.nikula@intel.com \
    --cc=keithp@keithp.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markus.heiser@darmarit.de \
    --cc=mchehab@osg.samsung.com \
    --cc=rdunlap@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.