From: Anders Darander <anders@chargestorm.se>
To: "openembedded-devel@lists.openembedded.org"
<openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-oe][RFC] Need for qmake_base.bbclass?
Date: Tue, 16 Aug 2011 11:09:09 +0200 [thread overview]
Message-ID: <20110816090908.GF22184@chargestorm.se> (raw)
In-Reply-To: <201108160959.36103.paul.eggleton@linux.intel.com>
* Paul Eggleton <paul.eggleton@linux.intel.com> [110816 10:59]:
> On Tuesday 16 August 2011 08:49:08 Anders Darander wrote:
> > I'd like to get rid of qmake_base.bbclass in oe-core.
> Presumably you mean "in meta-oe" here...
Yes, that's right. (I don't know what it is with me and e-mail the
latest couple of days...)
> > If we merge the second hunk of the diff to oe-core, do we risk getting
> > any failures/problems?
> Looks pretty reasonable to me, at a glance I can't see it causing any issues.
Good to hear. If no-one else has any objections, I'll submit a patch
delete qmake_base.bbclass, after submitting and getting my oe-core
patches merged.
Cheers,
Anders
--
Anders Darander
ChargeStorm AB
prev parent reply other threads:[~2011-08-16 9:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-16 7:49 [meta-oe][RFC] Need for qmake_base.bbclass? Anders Darander
2011-08-16 8:59 ` Paul Eggleton
2011-08-16 9:09 ` Anders Darander [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=20110816090908.GF22184@chargestorm.se \
--to=anders@chargestorm.se \
--cc=openembedded-devel@lists.openembedded.org \
/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.