From: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: Markus Heiser <markus.heiser@darmarit.de>,
Jonathan Corbet <corbet@lwn.net>,
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 10:06:55 -0300 [thread overview]
Message-ID: <20160701100655.587282a5@recife.lan> (raw)
In-Reply-To: <87furtpmre.fsf@intel.com>
Em Fri, 01 Jul 2016 15:26:45 +0300
Jani Nikula <jani.nikula@intel.com> escreveu:
> > In this example, the sphinx build is started as a side effect
> > even if it is not rebuild in this example, because nothing
> > in reST content has changed: "looking for now-outdated files... none found".
> >
> > As far as I can see, this is done **because** Makefile.sphinx
> > ignores DOCBOOK.
>
> I was referring to the original problem Mauro reported where the build
> failed. The above is a different issue, but an issue nonetheless. Patch
> sent.
Patches look ok, but that's not what I wanted ;) what I want is to
have something that Makefile.sphinx will look into and build just
the book described there. E. g. something like:
make BOOK="linux_tv" htmldocs
Would make sphinx to only build the book under the
Documentation/linux_tv directory.
--
Thanks,
Mauro
next prev parent reply other threads:[~2016-07-01 13:14 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 [this message]
2016-07-01 12:52 ` Mauro Carvalho Chehab
2016-07-01 12:58 ` Jonathan Corbet
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=20160701100655.587282a5@recife.lan \
--to=mchehab@osg.samsung.com \
--cc=airlied@gmail.com \
--cc=corbet@lwn.net \
--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=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.