All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Saul Wold <sgw@linux.intel.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] qt4e-demo-image: Fix bug 999
Date: Thu, 25 Aug 2011 01:13:20 +0100	[thread overview]
Message-ID: <201108250113.20066.paul.eggleton@linux.intel.com> (raw)
In-Reply-To: <4E558B0D.1080307@linux.intel.com>

On Thursday 25 August 2011 00:36:45 Saul Wold wrote:
> Why do we need the qt4e-base-image and this demo-image?  Do we expect to
> have multiple images?  This creates yet another image that needs to be
> built and tested?  Can this really just be added to the sato-sdk or
> lsb-sdk images instead?

No, it doesn't belong in sato-sdk and lsb-sdk is Qt4/X11 based which counts it 
out also. It really needs its own image. The -base image could be merged into 
-demo though.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



  reply	other threads:[~2011-08-25  0:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-24  6:34 [PATCH 0/1] qt4e-demo-image: Fix bug 999 Xiaofeng Yan
2011-08-24  6:34 ` [PATCH 1/1] " Xiaofeng Yan
2011-08-24 23:36   ` Saul Wold
2011-08-25  0:13     ` Paul Eggleton [this message]
2011-08-25  2:10       ` Xiaofeng Yan
  -- strict thread matches above, loose matches on Subject: below --
2011-09-05  1:47 [PATCH 0/1]:qt4e-demo-image: " Xiaofeng Yan
2011-09-05  1:47 ` [PATCH 1/1] qt4e-demo-image:Fix " Xiaofeng Yan
2011-08-23 10:57 [PATCH 0/1] qt4e-demo-image: Fix " Xiaofeng Yan
2011-08-23 10:57 ` [PATCH 1/1] " Xiaofeng Yan
2011-08-23 12:18   ` Paul Eggleton
2011-08-23 12:27     ` Koen Kooi
2011-08-23 12:53       ` Paul Eggleton
2011-08-23 15:10         ` Koen Kooi
2011-08-24  0:16           ` Saul Wold
2011-08-24  1:04             ` Paul Eggleton

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=201108250113.20066.paul.eggleton@linux.intel.com \
    --to=paul.eggleton@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=sgw@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.