From: Tom Rini <tom_rini@mentor.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v2 0/1] Resync siteinfo.bbclass with oe.dev
Date: Fri, 22 Jul 2011 09:49:02 -0700 [thread overview]
Message-ID: <4E29A9FE.4020205@mentor.com> (raw)
In-Reply-To: <4EFFABBF-7073-4B97-B5A5-F9DBF4B7C5DA@dominion.thruhere.net>
On 07/22/2011 08:35 AM, Koen Kooi wrote:
>
> Op 20 jul. 2011, om 22:50 heeft Tom Rini het volgende geschreven:
>
>> Hey all,
>>
>> This is the second of two pull requests. This doesn't depend on the first
>> request, it's just splitting changes up. There's three changes here. First,
>> site/ix86-common was setting the wrong value for unsigned int. Second,
>> change perl to use SITEINFO variables rather than functions.
>> We're down to one change now to re-sync siteinfo.bbclass with oe-core
>> and oe.dev. This re-works the functions a bit inside siteinfo.bbclass
>> to be easier to add new platforms (and hopefully multilibs) to.
>>
>> My next step is to work on merging and verifying as much as possible
>> the site files in oe-core and oe.dev.
>>
>> v2: Rework based on Richard's comments to not be a generator and just
>> return a string list again.
>
> Not that it has been merged, can the siteinfo from meta-oe get deleted?
The class? yes. It wasn't being used anyhow :)
--
Tom Rini
Mentor Graphics Corporation
prev parent reply other threads:[~2011-07-22 16:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-20 20:50 [PATCH v2 0/1] Resync siteinfo.bbclass with oe.dev Tom Rini
2011-07-20 20:50 ` [PATCH v2 1/1] siteinfo.bbclass: Port over oe.dev logic for site files Tom Rini
2011-07-25 9:57 ` Enrico Scholz
2011-07-27 17:49 ` Khem Raj
2011-07-22 15:23 ` [PATCH v2 0/1] Resync siteinfo.bbclass with oe.dev Saul Wold
2011-07-22 15:35 ` Koen Kooi
2011-07-22 16:49 ` Tom Rini [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=4E29A9FE.4020205@mentor.com \
--to=tom_rini@mentor.com \
--cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox