From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Tomas Frydrych <tf+lists.yocto@r-finger.com>
Cc: yocto@yoctoproject.org
Subject: Re: yocto beagleboard.conf -- should it not go away?
Date: Wed, 05 Sep 2012 22:43:13 +0100 [thread overview]
Message-ID: <1346881393.21985.97.camel@ted> (raw)
In-Reply-To: <1346849303.21985.56.camel@ted>
On Wed, 2012-09-05 at 13:48 +0100, Richard Purdie wrote:
> The root of the problem is that meta-yocto mixes up policy and hardware
> support which is bad. It also means its not compliant with the new Yocto
> Project compliance criteria and hence is not Yocto Project Compatible.
>
> Now we've got the compliance criteria sorted out there are some
> adjustments that need to be made and I will shortly be cleaving
> meta-yocto into two pieces to resolve this. I hadn't looked at this
> until now mainly in case there were changes to the criteria.
This has now been fixed in:
http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=2000698b17011bbde1c3e5bb01a7d6763316db5a
next prev parent reply other threads:[~2012-09-05 21:43 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-03 20:06 yocto beagleboard.conf -- should it not go away? Tomas Frydrych
2012-09-03 20:15 ` Bruce Ashfield
2012-09-03 20:55 ` Tomas Frydrych
2012-09-03 21:08 ` Bruce Ashfield
2012-09-04 8:21 ` Jack Mitchell
2012-09-04 12:24 ` Bruce Ashfield
2012-09-05 22:03 ` Richard Purdie
2012-09-04 8:58 ` Tomas Frydrych
2012-09-04 12:20 ` Bruce Ashfield
2012-09-04 17:18 ` Darren Hart
2012-09-04 20:25 ` William Mills
2012-09-04 23:23 ` Darren Hart
2012-09-05 14:20 ` William Mills
2012-09-05 14:42 ` Darren Hart
2012-09-05 15:16 ` Bruce Ashfield
2012-09-05 21:52 ` Richard Purdie
2012-09-05 8:49 ` Tomas Frydrych
2012-09-05 9:15 ` Paul Eggleton
2012-09-05 9:43 ` Tomas Frydrych
2012-09-05 12:48 ` Richard Purdie
2012-09-05 14:45 ` William Mills
2012-09-05 15:06 ` Tomas Frydrych
2012-09-05 15:44 ` Richard Purdie
2012-09-05 19:34 ` Martin Jansa
2012-09-05 21:43 ` Richard Purdie [this message]
2012-09-05 14:39 ` Darren Hart
2012-09-08 7:18 ` Khem Raj
2012-09-05 21:46 ` Richard Purdie
2012-09-06 5:39 ` Tomas Frydrych
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=1346881393.21985.97.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=tf+lists.yocto@r-finger.com \
--cc=yocto@yoctoproject.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.