All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH 4/4] qt4: remove bbappends
Date: Sat, 06 Apr 2013 20:28:26 +0100	[thread overview]
Message-ID: <7895477.XWUCIH5euc@helios> (raw)
In-Reply-To: <CAP9ODKpt1GX0pbHx-=HKsJ9-BkZfhxQiAcJVdBkc4iGhu-bg+g@mail.gmail.com>

On Saturday 06 April 2013 10:36:41 Otavio Salvador wrote:
> On Fri, Apr 5, 2013 at 8:35 PM, Paul Eggleton
> <paul.eggleton@linux.intel.com> wrote:
> > These changes to Qt's configuration need to be applied in distro layers,
> > not in meta-oe.
> > 
> > Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
> 
> NACK!
> 
> Keep PRINC as otherwise revision will go backwards.

Sigh... Oh well I guess Qt 4.8.5 is just around the corner and then we can 
drop this bbappend. When can we drop the packagegroup one though?

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



  reply	other threads:[~2013-04-06 19:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-05 23:35 [meta-oe][PATCH 0/4] Clean up recipes Paul Eggleton
2013-04-05 23:35 ` [meta-oe][PATCH 1/4] libmad: remove Paul Eggleton
2013-04-06 13:40   ` Otavio Salvador
2013-04-05 23:35 ` [meta-oe][PATCH 2/4] icon-naming-utils: remove Paul Eggleton
2013-04-06 13:41   ` Otavio Salvador
2013-04-05 23:35 ` [meta-oe][PATCH 3/4] packagegroup-qte-toolchain-target: remove bbappend Paul Eggleton
2013-04-06 13:37   ` Otavio Salvador
2013-04-05 23:35 ` [meta-oe][PATCH 4/4] qt4: remove bbappends Paul Eggleton
2013-04-06 13:36   ` Otavio Salvador
2013-04-06 19:28     ` Paul Eggleton [this message]
2013-04-06 20:55       ` Otavio Salvador
2013-04-06 13:42 ` [meta-oe][PATCH 0/4] Clean up recipes Otavio Salvador

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=7895477.XWUCIH5euc@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=otavio@ossystems.com.br \
    /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.