From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Cc: Ferruh Yigit <ferruh.yigit@intel.com>,
John McNamara <john.mcnamara@intel.com>,
Marko Kovacevic <marko.kovacevic@intel.com>
Subject: Re: [dpdk-dev] [PATCH] doc: fix PDF build
Date: Wed, 10 Jul 2019 09:44:12 +0200 [thread overview]
Message-ID: <2833305.GBnle41HQM@xps> (raw)
In-Reply-To: <56b4e556-6775-3b0c-4b41-b30501dcd95a@intel.com>
09/07/2019 18:53, Ferruh Yigit:
> On 7/9/2019 2:11 PM, Thomas Monjalon wrote:
> > The command "make doc-guides-pdf" is failing because
> > there are more than 1500 lines in the file MAINTAINERS
> > which is included in the contributing guide.
> >
> > We are facing the issue mentioned in this comment:
> > https://github.com/sphinx-doc/sphinx/issues/3099#issuecomment-256440704
> >
> > Anyway the file MAINTAINERS is mentioned several times in the guide.
> > So the "literalinclude" is removed from the guide to fix the build
> > of the PDF.
> >
> > Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
>
> Tested-by: Ferruh Yigit <ferruh.yigit@intel.com>
Applied
next prev parent reply other threads:[~2019-07-10 7:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-09 13:11 Thomas Monjalon
2019-07-09 16:53 ` Ferruh Yigit
2019-07-10 7:44 ` Thomas Monjalon [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-11-02 13:38 [dpdk-dev] [PATCH] doc: fix pdf build Marko Kovacevic
2018-11-02 15:17 ` Ferruh Yigit
2018-11-02 16:31 ` Mcnamara, John
2018-11-04 21:41 ` Thomas Monjalon
2018-11-02 16:44 ` Thomas Monjalon
2018-11-02 16:47 ` Kovacevic, Marko
2018-08-08 21:25 [dpdk-dev] [PATCH] doc: fix PDF build Thomas Monjalon
2018-08-08 21:29 ` Mokhtar, Amr
2018-08-08 22:03 ` 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=2833305.GBnle41HQM@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@intel.com \
/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).