From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Andreas Oberritter <obi@opendreambox.org>,
"Jolley, Stephen K" <stephen.k.jolley@intel.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: Yocto Project Status WW45 - UPDATED
Date: Tue, 08 Nov 2016 13:51:25 +0000 [thread overview]
Message-ID: <1478613085.23123.137.camel@linuxfoundation.org> (raw)
In-Reply-To: <e188c300-ce1b-4591-cb87-81a1497bbf34@opendreambox.org>
On Tue, 2016-11-08 at 11:00 +0100, Andreas Oberritter wrote:
> Hello Stephen,
>
> On 04.11.2016 18:06, Jolley, Stephen K wrote:
> >
> > · There was a challenging taskhash mismatch test case this
> > week
> > which has resulted in some significant debugging improvements for
> > taskhashes and basehashes which are now in master.
> is there an entry in bugzilla about this issue, or can you please add
> a reference to the actual commits in master? I'm facing a similar
> issue, so it might be helpful for me to backport them to the branch
> I'm using.
http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=0a4a6d6956a10aa0a6589de12b0b2380a9f0a7d9
has info in the commit message. You also want:
http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=589f08aa852dd43af5d05d698cfa917bec084210
http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=157947efc7e505e01baafb33ec93fe2f485308fe
http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=f6b0c60664e86fec55d282f1ea41238abd74712d
http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=71c837611690ab4bec1656a58d13ca48e7c6a6e6
Cheers,
Richard
next prev parent reply other threads:[~2016-11-08 13:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-04 17:06 Yocto Project Status WW45 - UPDATED Jolley, Stephen K
2016-11-04 17:49 ` akuster
2016-11-08 10:00 ` Andreas Oberritter
2016-11-08 13:51 ` Richard Purdie [this message]
2016-11-11 8:53 ` Andreas Oberritter
2016-11-11 18:20 ` akuster808
2016-11-11 18:49 ` Andreas Oberritter
2016-11-16 16:17 ` akuster808
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=1478613085.23123.137.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=obi@opendreambox.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=stephen.k.jolley@intel.com \
/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.