From: Koen Kooi <koen@dominion.thruhere.net>
To: Mark Hatle <mark.hatle@windriver.com>
Cc: yocto@yoctoproject.org
Subject: Re: Moving angstrom under the yocto banner
Date: Fri, 30 Mar 2012 12:33:28 -0700 [thread overview]
Message-ID: <26C6B15B-4A12-453A-A146-C884A5040178@dominion.thruhere.net> (raw)
In-Reply-To: <4F7608DC.1000402@windriver.com>
Op 30 mrt. 2012, om 12:26 heeft Mark Hatle het volgende geschreven:
> On 3/30/12 1:44 PM, Koen Kooi wrote:
>> Hi,
>>
>> RP said I should raise this on the yocto lists, so here it is:
>>
>> The Angstrom core team would like to move angstrom under the yocto banner so
>> we can formally claim to be 'yocto'.
>
> For it to be on the yocto project web site, it just need to have the layers hosted on the git.yoctoproject.org. But there is no "yocto".. It's the Yocto Project, Poky, or specific git repositories. There is no reason we can't have an angstrom repository. It could be in a similar format to the Poky repository (everything combined for a single download), or it could be a layer [or layers] that sit on top of Poky.
Why on top of poky? I do not want poky, nor do my customers, oe-core is what we need and want. This proposal to move angstrom under yocto is targeted at eliminating 'poky' from the stack while still being able to say 'yocto'.
We both know that saying it is 'yocto' is wrong and misleading, but that's what users are asking for and yocto advocates seem to push. Just watch the ELC videos for yocto related presentations, 'yocto' and 'poky' are used interchangeably in most of them.
A 'reference' should be just that, a reference, not a mandated part.
regards,
Koen
next prev parent reply other threads:[~2012-03-30 19:33 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-30 18:44 Moving angstrom under the yocto banner Koen Kooi
2012-03-30 19:00 ` Osier-mixon, Jeffrey
2012-04-10 14:04 ` Koen Kooi
2012-04-10 16:07 ` Stewart, David C
2012-03-30 19:26 ` Mark Hatle
2012-03-30 19:33 ` Koen Kooi [this message]
2012-03-30 20:18 ` Mark Hatle
2012-03-30 20:33 ` Koen Kooi
2012-03-30 20:45 ` Tom Rini
2012-03-30 20:51 ` Koen Kooi
2012-03-30 20:55 ` Osier-mixon, Jeffrey
2012-03-30 21:02 ` Eric Bénard
2012-03-30 21:01 ` Osier-mixon, Jeffrey
2012-03-30 21:12 ` Koen Kooi
2012-03-30 21:11 ` Richard Purdie
2012-03-30 23:06 ` Stewart, David C
2012-03-30 23:09 ` Chris Larson
2012-03-30 23:14 ` Tom Rini
2012-03-30 23:49 ` Tom Rini
2012-03-30 23:58 ` Koen Kooi
2012-03-30 23:52 ` Darren Hart
2012-03-31 0:08 ` Koen Kooi
2012-03-31 0:28 ` Darren Hart
2012-03-31 0:53 ` Koen Kooi
2012-03-31 1:21 ` Darren Hart
2012-03-31 1:37 ` Koen Kooi
2012-03-31 2:27 ` Darren Hart
2012-03-31 3:00 ` Chris Larson
2012-03-31 3:27 ` Darren Hart
2012-03-31 7:06 ` Richard Purdie
2012-03-31 10:00 ` Frans Meulenbroeks
2012-04-02 4:08 ` Matthew McClintock
2012-04-02 11:27 ` Richard Purdie
2012-04-02 17:13 ` Tom Rini
2012-04-03 16:01 ` Darren Hart
2012-04-03 16:25 ` Martin Jansa
2012-04-03 16:32 ` Darren Hart
2012-04-03 16:40 ` Tom Rini
2012-04-03 17:07 ` Darren Hart
2012-04-03 16:44 ` Martin Jansa
2012-04-03 17:08 ` Darren Hart
2012-04-03 17:15 ` Tom Rini
2012-04-03 17:26 ` Chris Larson
2012-04-03 17:34 ` Brian Hutchinson
2012-04-03 18:03 ` Darren Hart
2012-03-31 16:30 ` Khem Raj
2012-04-01 0:51 ` Chris Larson
2012-03-31 15:37 ` Paul Eggleton
2012-03-30 22:32 Daniel Lazzari
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=26C6B15B-4A12-453A-A146-C884A5040178@dominion.thruhere.net \
--to=koen@dominion.thruhere.net \
--cc=mark.hatle@windriver.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.