From: Mauro Carvalho Chehab <mchehab@s-opensource.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@infradead.org>
Subject: Re: [PATCH 0/9] Prepare Sphinx to build media PDF books
Date: Fri, 19 Aug 2016 10:24:27 -0300 [thread overview]
Message-ID: <20160819102427.29f41d3c@vento.lan> (raw)
In-Reply-To: <20160818172127.190fad79@lwn.net>
Em Thu, 18 Aug 2016 17:21:27 -0600
Jonathan Corbet <corbet@lwn.net> escreveu:
> On Tue, 16 Aug 2016 13:25:34 -0300
> Mauro Carvalho Chehab <mchehab@s-opensource.com> wrote:
>
> > I think this patch series belong to docs-next. Feel free to merge them there, if
> > you agree. There's one extra patch that touches Documentation/conf.py,
> > re-adding the media book to the PDF build, but IMHO this one would be better
> > to be merged via the media tree, after the fixes inside the media documentation
> > to fix the build.
>
> It's now in docs-next. I was able to build some nice-looking docs with it
> without too much (additional) pain...
Good!
> The conf.py patch makes me a bit nervous, in that I feel like I spent a
> fair amount of time explaining docs merge conflicts to Linus during the
> merge window, and would rather not do that again. Can we keep it aside,
> with the idea that one of us will put it in toward the end of the 4.9
> merge window?
Yeah, sure. I'm actually planning to pull from your docs-next branch
at the media master tree before starting picking other patches on it,
and wait for your pull request before sending mine on the next merge
tree.
> Meanwhile, let's see how this xelatex thing works out. Thanks for making
> all this work!
Anytime!
Thanks,
Mauro
next prev parent reply other threads:[~2016-08-19 13:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-16 16:25 [PATCH 0/9] Prepare Sphinx to build media PDF books Mauro Carvalho Chehab
2016-08-16 16:25 ` [PATCH 1/9] docs-rst: fix a breakage when building PDF documents Mauro Carvalho Chehab
2016-08-16 16:25 ` [PATCH 2/9] docs-rst: remove a rst2pdf left over code Mauro Carvalho Chehab
2016-08-16 16:25 ` [PATCH 3/9] docs-rst: allow generating some LaTeX pages in landscape Mauro Carvalho Chehab
2016-08-16 16:25 ` [PATCH 4/9] docs-rst: improve output for .. notes:: on LaTeX Mauro Carvalho Chehab
2016-08-16 16:25 ` [PATCH 5/9] docs-rst: Don't mangle with UTF-8 chars on LaTeX/PDF output Mauro Carvalho Chehab
2016-08-16 16:25 ` [PATCH 6/9] docs-rst: better adjust margins and font size Mauro Carvalho Chehab
2016-08-16 16:25 ` [PATCH 7/9] docs-rst: parse-heraders.pl: escape LaTeX characters Mauro Carvalho Chehab
2016-08-16 16:25 ` [PATCH 8/9] docs-rst: Don't go to interactive mode on errors Mauro Carvalho Chehab
2016-08-16 16:25 ` [PATCH 9/9] docs-rst: enable the Sphinx math extension Mauro Carvalho Chehab
2016-08-18 23:21 ` [PATCH 0/9] Prepare Sphinx to build media PDF books Jonathan Corbet
2016-08-19 13:24 ` Mauro Carvalho Chehab [this message]
2016-08-24 10:42 ` Mauro Carvalho Chehab
2016-08-24 11:46 ` Markus Heiser
2016-08-24 12:23 ` 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=20160819102427.29f41d3c@vento.lan \
--to=mchehab@s-opensource.com \
--cc=corbet@lwn.net \
--cc=linux-media@vger.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