Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [dylan][PATCH 0/1] Fix Hob not starting in the build appliance
Date: Thu, 20 Mar 2014 19:04:54 +0000	[thread overview]
Message-ID: <cover.1395342113.git.paul.eggleton@linux.intel.com> (raw)

Fixes the bug found by QA in the 1.4.3 build appliance (bug 5941 - tested
this time).


The following changes since commit 30d3f06fddea2d8f3537d3415c95d75a6487078c:

  sstate: Drop 'SafeDep' code from setscene validation function (2014-03-17 23:17:03 +0000)

are available in the git repository at:

  git://git.openembedded.org/openembedded-core-contrib paule/dylan-python
  http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paule/dylan-sstate

Saul Wold (1):
  packagegroup-self-hosted: Add missing python code

 meta/recipes-core/packagegroups/packagegroup-self-hosted.bb | 5 +++++
 1 file changed, 5 insertions(+)

-- 
1.8.5.3



             reply	other threads:[~2014-03-20 19:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-20 19:04 Paul Eggleton [this message]
2014-03-20 19:04 ` [dylan][PATCH 1/1] packagegroup-self-hosted: Add missing python code Paul Eggleton

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=cover.1395342113.git.paul.eggleton@linux.intel.com \
    --to=paul.eggleton@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox