Openembedded Bitbake Development
 help / color / mirror / Atom feed
From: Liming An <limingx.l.an@intel.com>
To: bitbake-devel@lists.openembedded.org
Subject: [PATCH 0/2] hob:bug-fixes
Date: Thu,  2 Aug 2012 19:05:55 +0800	[thread overview]
Message-ID: <cover.1343905168.git.limingx.l.an@intel.com> (raw)

The following changes since commit 62d42fe3cfa575cb97b484ccf7b2e9a25cc50770:

  tiny-init: Setup /dev/ptmx in init (2012-08-01 23:11:18 +0100)

are available in the git repository at:
  git://git.pokylinux.org/poky-contrib limx/hob-bug-fixes-continue
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=limx/hob-bug-fixes-continue

Liming An (2):
  Hob: log for Hob and allow users to show logs after successful build
  Hob: change the Build failure scenario as ui design

 bitbake/lib/bb/ui/crumbs/builddetailspage.py     |   83 +++++++++-------------
 bitbake/lib/bb/ui/crumbs/builder.py              |   52 +++++++++++---
 bitbake/lib/bb/ui/crumbs/hobeventhandler.py      |    3 +
 bitbake/lib/bb/ui/crumbs/imagedetailspage.py     |   24 +++++-
 bitbake/lib/bb/ui/crumbs/packageselectionpage.py |   27 ++++++-
 bitbake/lib/bb/ui/crumbs/runningbuild.py         |   41 +++++++++++
 6 files changed, 162 insertions(+), 68 deletions(-)

-- 
1.7.5.4




             reply	other threads:[~2012-08-02 11:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-02 11:05 Liming An [this message]
2012-08-02 11:06 ` [PATCH 1/2] Hob: log for Hob and allow users to show logs after successful build Liming An
2012-08-02 11:06 ` [PATCH 2/2] Hob: change the Build failure scenario as ui design Liming An
  -- strict thread matches above, loose matches on Subject: below --
2012-06-14 12:21 [PATCH 0/2] Hob: bug-fixes Liming An
2012-06-14 12:55 ` Richard Purdie
2012-05-30 12:01 Liming An
2012-05-30 16:19 ` Richard Purdie

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.1343905168.git.limingx.l.an@intel.com \
    --to=limingx.l.an@intel.com \
    --cc=bitbake-devel@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