From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: bitbake-devel <bitbake-devel@lists.openembedded.org>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: RFC: update_data removal
Date: Fri, 05 Jun 2015 13:14:32 +0100 [thread overview]
Message-ID: <1433506472.19831.18.camel@linuxfoundation.org> (raw)
In-Reply-To: <1432766602.404.90.camel@linuxfoundation.org>
On Wed, 2015-05-27 at 23:43 +0100, Richard Purdie wrote:
> I've been experimenting with this and I do have a branch which basically
> works:
>
> http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=rpurdie/noupdatedata5
Testing showed up some issues. I've addressed those and this code is now
as a bitbake branch at:
http://git.openembedded.org/bitbake/log/?h=noupdatedata
This now builds ok on the autobuilder. There is a small issue with
bitbake-selftest, I've a patch pending to address that (its a minor
tweak).
I've also sent a few patches to OE-Core to address issues these changes
showed up which I believe are omissions in the metadata.
Cheers,
Richard
prev parent reply other threads:[~2015-06-05 12:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 22:43 RFC: update_data removal Richard Purdie
2015-06-05 12:14 ` Richard Purdie [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=1433506472.19831.18.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=bitbake-devel@lists.openembedded.org \
--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