From: "Kovacevic, Marko" <marko.kovacevic@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Mcnamara, John" <john.mcnamara@intel.com>,
"ciara.power@intel.com" <ciara.power@intel.com>
Subject: Re: [dpdk-dev] [PATCH] doc: fix pdf build
Date: Fri, 2 Nov 2018 16:47:16 +0000 [thread overview]
Message-ID: <6DC05C7C5F25994B81B3F2F214251F660204C99A@IRSMSX104.ger.corp.intel.com> (raw)
In-Reply-To: <2356157.kdXkEZGcT8@xps>
All appreciations can be shown here Thomas :)
https://mobro.co/13793316
And had help from John :)
> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas@monjalon.net]
> Sent: Friday, November 2, 2018 4:44 PM
> To: Kovacevic, Marko <marko.kovacevic@intel.com>
> Cc: dev@dpdk.org; Mcnamara, John <john.mcnamara@intel.com>;
> ciara.power@intel.com
> Subject: Re: [PATCH] doc: fix pdf build
>
> 02/11/2018 14:38, Marko Kovacevic:
> > PDF build was failing in the howto guides found the weird character
> > causing the issue
> [...]
> > -* Python ≥ 2.5
> > +* Python >= 2.5
>
> I spent some time on it and gave up.
> You are my hero :)
>
>
next prev parent reply other threads:[~2018-11-02 16:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-02 13:38 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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-07-09 13:11 [dpdk-dev] [PATCH] doc: fix PDF build Thomas Monjalon
2019-07-09 16:53 ` Ferruh Yigit
2019-07-10 7:44 ` Thomas Monjalon
2018-08-08 21:25 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=6DC05C7C5F25994B81B3F2F214251F660204C99A@IRSMSX104.ger.corp.intel.com \
--to=marko.kovacevic@intel.com \
--cc=ciara.power@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--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).