From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Shane Wang <shane.wang@intel.com>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH 0/1] Hob: fix 2098
Date: Sun, 25 Mar 2012 12:14:18 +0100 [thread overview]
Message-ID: <1332674058.28414.77.camel@ted> (raw)
In-Reply-To: <cover.1332518429.git.shane.wang@intel.com>
On Sat, 2012-03-24 at 00:01 +0800, Shane Wang wrote:
> This patch is to fix bug 2098 to make the build progress clear.
>
> The following changes since commit 8350c03eeca3f5d70984797ef784f29c71cbbb3b:
>
> gst-plugins: remove obsolete orcc hack (2012-03-23 12:13:09 +0000)
>
> are available in the git repository at:
> git://git.pokylinux.org/poky-contrib shane/hob-fixes-1
> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=shane/hob-fixes-1
>
> Shane Wang (1):
> Hob: add build status labels in the build details screen to make it
> more close to the visual design
Merged to master, thanks.
Richard
prev parent reply other threads:[~2012-03-25 11:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-23 16:01 [PATCH 0/1] Hob: fix 2098 Shane Wang
2012-03-23 16:05 ` [PATCH 1/1] Hob: add build status labels in the build details screen to make it more close to the visual design Shane Wang
2012-03-25 11:14 ` 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=1332674058.28414.77.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=bitbake-devel@lists.openembedded.org \
--cc=shane.wang@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.