From: Richard Purdie <richard.purdie@intel.com>
To: "Perez Carranza, Jose" <jose.perez.carranza@intel.com>,
"yocto@yoctoproject.org" <yocto@yoctoproject.org>
Cc: "otavio@ossystems.com.br" <otavio@ossystems.com.br>,
"Lock, Joshua G" <joshua.g.lock@intel.com>
Subject: Re: Release Candidate Build for yocto-2.3.1. now available.
Date: Mon, 21 Aug 2017 21:43:55 +0100 [thread overview]
Message-ID: <1503348235.32591.69.camel@intel.com> (raw)
In-Reply-To: <0A5D9A624DF90343892F8F3FE7DE525A16A36FCE@fmsmsx101.amr.corp.intel.com>
On Mon, 2017-08-21 at 12:03 -0700, Perez Carranza, Jose wrote:
> This mail is kind of strange, artifacts are not published, there are
> not rc specified and afaiu we worked on QA for pyro 2.3.1 last
> month.
>
> Can anyone clarify this?
The eSDK artefacts in 2.3.1 were broken and its had to be rebuilt as
they were not functional. We're having some issues with the rebuilds
too :(.
Cheers,
Richard
next prev parent reply other threads:[~2017-08-21 20:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-21 18:00 Release Candidate Build for yocto-2.3.1. now available pokybuild
2017-08-21 19:03 ` Perez Carranza, Jose
2017-08-21 20:43 ` Richard Purdie [this message]
2017-08-22 23:36 ` Cruz, Libertad
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=1503348235.32591.69.camel@intel.com \
--to=richard.purdie@intel.com \
--cc=jose.perez.carranza@intel.com \
--cc=joshua.g.lock@intel.com \
--cc=otavio@ossystems.com.br \
--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.