From: Thomas Monjalon <thomas@monjalon.net>
To: Luca Boccassi <bluca@debian.org>
Cc: stable@dpdk.org, dev@dpdk.org, john.mcnamara@intel.com,
marko.kovacevic@intel.com
Subject: Re: [dpdk-stable] [PATCH] doc: fix garbage text in generated HTML guides
Date: Wed, 19 Dec 2018 03:28:55 +0100 [thread overview]
Message-ID: <1779038.8Nb24oYqjg@xps> (raw)
In-Reply-To: <20181205142545.24633-1-bluca@debian.org>
05/12/2018 15:25, Luca Boccassi:
> If the user has MAKEFLAGS set in the environment when building the
> documentation, the doc/guides/conf.py script which calls "make"
> exclusively to get the project version might pick up garbage from
> stdout, like:
>
> <title>FAQ — Data Plane Development Kit make[2]:
> Entering directory '/build/1st/dpdk-18.11/doc/guides'
> 18.11.0
> make[2]: Leaving directory '/build/1st/dpdk-18.11'
> documentation</title>
>
> Override MAKEFLAGS in the Python subprocess call to avoid this issue.
>
> Fixes: f7aaae2fe6f7 ("doc: add copyright and version")
> Cc: stable@dpdk.org
>
> Signed-off-by: Luca Boccassi <bluca@debian.org>
Applied, thanks
prev parent reply other threads:[~2018-12-19 2:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-05 14:25 Luca Boccassi
2018-12-19 2:28 ` Thomas Monjalon [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=1779038.8Nb24oYqjg@xps \
--to=thomas@monjalon.net \
--cc=bluca@debian.org \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@intel.com \
--cc=stable@dpdk.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 NNTP newsgroup(s).