From: Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
Cc: "devicetree-spec-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<devicetree-spec-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Grant Likely <grant.likely-5wv7dgnIgG8@public.gmane.org>
Subject: Re: [RFC] Fix changebar pdf build and add to Travis releases
Date: Fri, 15 Dec 2017 16:46:12 -0600 [thread overview]
Message-ID: <CAL_Jsq+G6+o8OyZvQRk9VuJNzrZbx-Csbp2QVBtj4LwP4HT_MQ@mail.gmail.com> (raw)
In-Reply-To: <20171215141912.14414-1-grant.likely-5wv7dgnIgG8@public.gmane.org>
On Fri, Dec 15, 2017 at 8:19 AM, Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org> wrote:
> Fix the changebar build caused by a bad interaction between Sphinx and
> latexdiff. latexdiff was not doing the right thing for changes in
> chapter headers due to "red" and "blue" getting uppercased to "RED" and
> "BLUE", and creating invalid output when adding some verbatim sections.
> Fixed by moving to latest latexdiff and adding sphinxVerbatim to the
> VERBATIMENV config variable.
>
> Also update the travis-ci control file to also build the changebar
> version of the document.
>
> Cc: Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
> Signed-off-by: Grant Likely <grant.likely-5wv7dgnIgG8@public.gmane.org>
> ---
> Hi Rob,
>
> I've not figured out how to test this yet. I'll ping you on IRC about running it through its paces before committing the patch.
I fixed up an issue with wget and a missing package dependency and pushed.
Rob
prev parent reply other threads:[~2017-12-15 22:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-15 14:19 [RFC] Fix changebar pdf build and add to Travis releases Grant Likely
[not found] ` <20171215141912.14414-1-grant.likely-5wv7dgnIgG8@public.gmane.org>
2017-12-15 22:46 ` Rob Herring [this message]
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=CAL_Jsq+G6+o8OyZvQRk9VuJNzrZbx-Csbp2QVBtj4LwP4HT_MQ@mail.gmail.com \
--to=robh-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=devicetree-spec-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=grant.likely-5wv7dgnIgG8@public.gmane.org \
--cc=grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.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 read-only IMAP folder(s) and NNTP newsgroup(s).