From: Denys Dmytriyenko <denis@denix.org>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>,
"yocto@yoctoproject.org" <yocto@yoctoproject.org>,
SatyaNarayana Sampangi <satya.2891@gmail.com>
Subject: Re: Devtool: Script Not found
Date: Thu, 2 Mar 2017 11:48:40 -0500 [thread overview]
Message-ID: <20170302164840.GN7350@denix.org> (raw)
In-Reply-To: <CAJTo0LYKK6HGgvg-qV4BgXxf5=43X=tEv8y-ncnpV6nC8S5M4A@mail.gmail.com>
On Thu, Mar 02, 2017 at 04:26:32PM +0000, Burton, Ross wrote:
> On 2 March 2017 at 16:25, SatyaNarayana Sampangi <satya.2891@gmail.com>
> wrote:
>
> >
> > Pls go through this link,
> >
> > https://www.yoctoproject.org/product/meta-ti-bsp-layer
> >
> > very clearly mentioned
> >
>
> Clearly the meta-ti maintainers should update the site.
meta-ti maintainers have no control over that page.
It says "compatible" as defined in "Yocto Project Compatible 1.0":
https://www.yoctoproject.org/ecosystem/yocto-project-branding-program
That program has been in the process of upgrading and I've been asked to
wait for the new and improved "Yocto Project Compatible 2.0" process...
So, technically, meta-ti is still following the rules and adhering to the
compatibility guidelines all the way to version 2.2, just not running the
official review process for the old program...
BTW, meta-ti says compatible with version 1.6, while meta-intel is 1.5:
https://www.yoctoproject.org/product/meta-intel-bsp-layer
So, clearly, the process has been abandoned by everyone...
--
Denys
next prev parent reply other threads:[~2017-03-02 16:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-02 14:26 Devtool: Script Not found SatyaNarayana Sampangi
2017-03-02 15:48 ` Leonardo Sandoval
2017-03-02 15:59 ` Burton, Ross
2017-03-02 16:14 ` SatyaNarayana Sampangi
2017-03-02 16:19 ` Burton, Ross
2017-03-02 16:25 ` SatyaNarayana Sampangi
2017-03-02 16:26 ` Burton, Ross
[not found] ` <CAF1M0z7UKFzAovgMYd_BWPTi2nWQQ69AjSVOvCO_j0Bej=iTGA@mail.gmail.com>
2017-03-02 16:34 ` SatyaNarayana Sampangi
2017-03-02 16:48 ` Denys Dmytriyenko [this message]
2017-03-02 16:56 ` Denys Dmytriyenko
2017-03-02 21:01 ` SatyaNarayana Sampangi
2017-03-02 23:02 ` Denys Dmytriyenko
2017-03-03 4:36 ` SatyaNarayana Sampangi
2017-03-05 17:09 ` SatyaNarayana Sampangi
2017-03-13 16:59 ` Denys Dmytriyenko
2017-03-02 16:20 ` Gary Thomas
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=20170302164840.GN7350@denix.org \
--to=denis@denix.org \
--cc=paul.eggleton@linux.intel.com \
--cc=ross.burton@intel.com \
--cc=satya.2891@gmail.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.