DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Mcnamara, John" <john.mcnamara@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] doc: remove dejavu font from doc build
Date: Sun, 1 Nov 2015 19:37:26 +0000	[thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE202395A8B@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <2704812.sOoAmbxRg4@xps13>

> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> Sent: Sunday, November 1, 2015 6:32 PM
> To: Mcnamara, John
> Cc: dev@dpdk.org
> Subject: Re: [PATCH v2] doc: remove dejavu font from doc build
> 
> 2015-11-01 16:35, Mcnamara, John:
> > > -----Original Message-----
> > > From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> > > Sent: Sunday, November 1, 2015 3:00 PM
> > > To: Mcnamara, John
> > > Cc: dev@dpdk.org
> > > Subject: Re: [PATCH v2] doc: remove dejavu font from doc build


> > Mainly because the requirements are now at the minimum with only one
> package required.
> 
> If we don't give tips about how to install a minimum texlive, it means we
> have to install the whole texlive distribution which is a huge dependency.

Ok. I'll put that back in.

  reply	other threads:[~2015-11-01 19:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-20 11:32 [dpdk-dev] [PATCH] " John McNamara
2015-10-23 16:09 ` Van Haaren, Harry
2015-10-26 14:24 ` Thomas Monjalon
2015-10-26 17:35   ` Mcnamara, John
     [not found]   ` <B27915DBBA3421428155699D51E4CFE202392CBC@IRSMSX103.ger.corp.intel.com>
2015-10-29 12:17     ` Thomas Monjalon
2015-11-01 14:13 ` [dpdk-dev] [PATCH v2] " John McNamara
2015-11-01 14:59   ` Thomas Monjalon
2015-11-01 16:35     ` Mcnamara, John
2015-11-01 18:32       ` Thomas Monjalon
2015-11-01 19:37         ` Mcnamara, John [this message]
2015-11-01 20:17 ` [dpdk-dev] [PATCH v3] " John McNamara
2015-12-13 21:14   ` 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=B27915DBBA3421428155699D51E4CFE202395A8B@IRSMSX103.ger.corp.intel.com \
    --to=john.mcnamara@intel.com \
    --cc=dev@dpdk.org \
    --cc=thomas.monjalon@6wind.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).