From: Joshua Lock <josh@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/3] Various hob fixes
Date: Mon, 19 Sep 2011 15:41:42 -0700 [thread overview]
Message-ID: <cover.1316471892.git.josh@linux.intel.com> (raw)
This series contains 3 bug fixes.
The first has been submitted previously but hasn't been applied or commented
on so I've rolled it into this pull request.
Patch one and two contain bug fixes for reported issues, patch three is a
minor change but a noticable one should one stumble accross it.
Please review and consider for master and the Yocto 1.1 release.
Regards,
Joshua
The following changes since commit 3e7f8afeacf7c8c8de3e87778a3907e33d4a06b3:
fetch2/git: fix subpath destination directory (2011-09-19 12:33:38 +0100)
are available in the git repository at:
git://github.com/incandescant/bitbake hob
https://github.com/incandescant/bitbake/tree/hob
Joshua Lock (3):
ui/crumbs/hobprefs: re-enable reloading of data after prefs changes
hob: fix build again when building packages only
hob: enable package only builds even if an image has been built
lib/bb/ui/crumbs/hobeventhandler.py | 13 +++++--------
lib/bb/ui/crumbs/hobprefs.py | 2 +-
lib/bb/ui/hob.py | 12 ++++++++----
3 files changed, 14 insertions(+), 13 deletions(-)
--
1.7.6.2
next reply other threads:[~2011-09-19 22:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-19 22:41 Joshua Lock [this message]
2011-09-19 22:41 ` [PATCH 1/3] ui/crumbs/hobprefs: re-enable reloading of data after prefs changes Joshua Lock
2011-09-19 22:41 ` [PATCH 2/3] hob: fix build again when building packages only Joshua Lock
2011-09-19 22:41 ` [PATCH 3/3] hob: enable package only builds even if an image has been built Joshua Lock
2011-09-20 15:00 ` [PATCH 0/3] Various hob fixes Joshua Lock
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.1316471892.git.josh@linux.intel.com \
--to=josh@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