From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Mcnamara, John" <john.mcnamara@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] mk: create pdf docs as a separate make target
Date: Fri, 27 Mar 2015 16:50:12 +0100 [thread overview]
Message-ID: <3924910.e08iILMsGh@xps13> (raw)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE2EF1794@IRSMSX103.ger.corp.intel.com>
2015-03-27 14:40, Mcnamara, John:
> I acked the patch that introduced this change but we've had a number of
> complaints from devs who don't want to or can't correctly install the
> (largish) toolchain for PDF generation, or if they do, don't like the
> extra time it takes.
You forgot to quote my previous explanation.
I don't understand the complaints as they can build only HTML if they want.
next prev parent reply other threads:[~2015-03-27 15:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-27 14:34 John McNamara
2015-03-27 14:40 ` Mcnamara, John
2015-03-27 15:50 ` Thomas Monjalon [this message]
2015-03-27 15:27 ` Thomas Monjalon
2015-03-27 16:03 ` Mcnamara, John
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=3924910.e08iILMsGh@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@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).