From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Poky Build User <pokybuild@yocto-www.yoctoproject.org>,
yocto@yoctoproject.org
Cc: joshua.g.lock@intel.com, alexandru.c.georgescu@intel.com,
otavio@ossystems.com.br
Subject: Re: Release Candidate Build for yocto-2.3.rc3 now available.
Date: Mon, 01 May 2017 18:21:28 +0100 [thread overview]
Message-ID: <1493659288.23535.44.camel@linuxfoundation.org> (raw)
In-Reply-To: <1493625516.23535.20.camel@linuxfoundation.org>
On Mon, 2017-05-01 at 08:58 +0100, Richard Purdie wrote:
> On Sat, 2017-04-29 at 19:25 +0000, Poky Build User wrote:
> >
> > A release candidate build for yocto-2.3.rc3 is now available at:
> >
> >
> > http://autobuilder.yoctoproject.org/pub/releases/yocto-2.3.rc3
> >
> >
> > Please begin QA on this build as soon as possible.
> >
> >
> > Build hash information:
> > meta-intel : 112643bbb731a6ccac7f4f5bde7f78d8fa2f9c15
> > meta-qt4 : e120a2193be3982d55741fb9e51472db6ab9a5cd
> > meta-mingw : 4bdb99650a053f254ccd158a6d0c25c80e79f6ee
> > meta-qt3 : f33b73a9563f2dfdfd0ee37b61d65d90197a456f
> > meta-gplv2 : de001bd6bfcec943d274b649c62be6848cc9c3e6
> > poky : a00f8981d8d2b361cc2c5d08d7cc6040c79af3cb
> >
> > \nThis is an automated message from\nThe Yocto Project
> > Autobuilder\nGit: git://git.yoctoproject.org/yocto-
> > autobuilder\nEmail: joshua.g.lock@intel.com
> We've found another problem so please wait for an rc4 build.
The rc4 build is in progress on the autobuilder and should be done
soon. If you want to hit the ground running current pyro/master are the
correct revisions.
Cheers,
Richard
prev parent reply other threads:[~2017-05-01 17:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-29 19:25 Release Candidate Build for yocto-2.3.rc3 now available Poky Build User
2017-05-01 7:58 ` Richard Purdie
2017-05-01 17:21 ` 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=1493659288.23535.44.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alexandru.c.georgescu@intel.com \
--cc=joshua.g.lock@intel.com \
--cc=otavio@ossystems.com.br \
--cc=pokybuild@yocto-www.yoctoproject.org \
--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.