From: "Mcnamara, John" <john.mcnamara@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>,
"dev@dpdk.org" <dev@dpdk.org>,
"Kovacevic, Marko" <marko.kovacevic@intel.com>
Cc: "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 1/3] doc: robustify PDF build
Date: Thu, 23 May 2019 11:16:10 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE23F642717@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <20190522202842.19818-2-thomas@monjalon.net>
> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas@monjalon.net]
> Sent: Wednesday, May 22, 2019 9:29 PM
> To: dev@dpdk.org; Mcnamara, John <john.mcnamara@intel.com>; Kovacevic,
> Marko <marko.kovacevic@intel.com>
> Cc: stable@dpdk.org
> Subject: [PATCH 1/3] doc: robustify PDF build
>
> In some environment like the current dpdk.org server, there can be some
> errors due to symbols in titles, as it was the case before this commit in
> DPDK 18.05:
> 551d148944dc ("doc: remove flow API migration section")
>
> ! LaTeX Error: Bad math environment delimiter.
>
> It can be avoided thanks to the Latex command \robustify.
>
Acked-by: John McNamara <john.mcnamara@intel.com>
next prev parent reply other threads:[~2019-05-23 11:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-22 20:28 [dpdk-dev] [PATCH 0/3] fix PDF doc build Thomas Monjalon
2019-05-22 20:28 ` [dpdk-dev] [PATCH 1/3] doc: robustify PDF build Thomas Monjalon
2019-05-23 11:16 ` Mcnamara, John [this message]
2019-05-22 20:28 ` [dpdk-dev] [PATCH 2/3] doc: fix PDF with greek letter Thomas Monjalon
2019-05-23 11:16 ` Mcnamara, John
2019-05-22 20:28 ` [dpdk-dev] [PATCH 3/3] doc: clean PDF config Thomas Monjalon
2019-05-23 11:16 ` Mcnamara, John
2019-05-29 11:04 ` [dpdk-dev] [PATCH 0/3] fix PDF doc build Thomas Monjalon
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=B27915DBBA3421428155699D51E4CFE23F642717@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=dev@dpdk.org \
--cc=marko.kovacevic@intel.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
/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).