From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Liming An <limingx.l.an@intel.com>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH 0/5] Hob: bug-fixes
Date: Wed, 23 May 2012 11:25:41 +0100 [thread overview]
Message-ID: <1337768741.8248.54.camel@ted> (raw)
In-Reply-To: <cover.1337610738.git.limingx.l.an@intel.com>
On Mon, 2012-05-21 at 22:41 +0800, Liming An wrote:
> The following changes since commit 2219caa312822cf756b88b07dd70a014404e9cb0:
>
> tune-mips64.inc: Add new tune file for mips64 big-endian (2012-05-21 09:59:04 +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 (5):
> Hob: add '--select a machine--' and '--select a base image--' to GUI
> Hob: change the build failure scenario as ui design
> Hob: fixed the issue about bug 'running image' workflow and related
> view
> Hob: fixed the line width of base image description view
> Hob: fixed the issue about the 'run image' page should have the
> primary bug
Merged to master, thanks.
I'm assuming the question from Shane will be addressed in a follow up
patch.
Cheers,
Richard
prev parent reply other threads:[~2012-05-23 10:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-21 14:41 [PATCH 0/5] Hob: bug-fixes Liming An
2012-05-21 14:41 ` [PATCH 1/5] Hob: add '--select a machine--' and '--select a base image--' to GUI Liming An
2012-05-21 14:41 ` [PATCH 2/5] Hob: change the build failure scenario as ui design Liming An
2012-05-21 14:41 ` [PATCH 3/5] Hob: fixed the issue about bug 'running image' workflow and related view Liming An
2012-05-21 14:41 ` [PATCH 4/5] Hob: fixed the line width of base image description view Liming An
2012-05-21 14:41 ` [PATCH 5/5] Hob: fixed the issue about the 'run image' page should have the primary bug Liming An
2012-05-23 6:09 ` Wang, Shane
2012-05-23 10:25 ` 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=1337768741.8248.54.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=bitbake-devel@lists.openembedded.org \
--cc=limingx.l.an@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox