Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Hongxu Jia <hongxu.jia@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: Saul Wold <saul.wold@intel.com>,
	OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/8] support xmlto
Date: Wed, 9 Jul 2014 09:31:37 +0800	[thread overview]
Message-ID: <53BC9B79.8060708@windriver.com> (raw)
In-Reply-To: <CAJTo0Lbsf6fw=rg3mQv7CqJ+Apmxd2X6W=srNf6dNer_5VZqNQ@mail.gmail.com>

On 07/09/2014 05:33 AM, Burton, Ross wrote:
> As such this is definitely a two-part series.  Adding xmlto is useful
> and I'm genuinely happy that someone who wasn't me managed to get
> docbook-xsl working;)  as that's the blocker for gtk-doc support too.
> However rnabling xmlto in some recipes globally isn't the right thing
> to do and will introduce noticeable regressions in build time for many
> classes of users for no reason.

Got it, I will send V2 without enable xmlto in some recipes.

//Hongxu


      parent reply	other threads:[~2014-07-09  1:31 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-08  9:47 [PATCH 0/8] support xmlto Hongxu Jia
2014-07-08  9:47 ` [PATCH 1/8] libxml2: enable Catalog support Hongxu Jia
2014-07-08 15:26   ` Burton, Ross
2014-07-08  9:47 ` [PATCH 2/8] docbook-xml: add docbook-xsl-stylesheets 1.78.1 Hongxu Jia
2014-07-08  9:47 ` [PATCH 3/8] docbook-xml: add docbook-xml-dtd4 Hongxu Jia
2014-07-08 10:03   ` Hongxu Jia
2014-07-08  9:47 ` [PATCH 4/8] xmlto: add version 0.0.25 Hongxu Jia
2014-07-08  9:47 ` [PATCH 5/8] alsa-utils: enable xmlto Hongxu Jia
2014-07-08  9:47 ` [PATCH 6/8] xorg-proto-common.inc: " Hongxu Jia
2014-07-08  9:47 ` [PATCH 7/8] xorg-lib-common.inc: " Hongxu Jia
2014-07-08  9:48 ` [PATCH 8/8] xserver-xorg.inc: " Hongxu Jia
2014-07-08 18:53   ` Otavio Salvador
2014-07-08 18:57 ` [PATCH 0/8] support xmlto Otavio Salvador
2014-07-08 21:33 ` Burton, Ross
2014-07-09  0:57   ` Otavio Salvador
2014-07-09  1:31   ` Hongxu Jia [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=53BC9B79.8060708@windriver.com \
    --to=hongxu.jia@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.com \
    --cc=saul.wold@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