From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Joshua Lock <josh@linux.intel.com>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH 0/4] Bug fixes for hob
Date: Tue, 09 Aug 2011 15:20:33 +0100 [thread overview]
Message-ID: <1312899633.14274.304.camel@rex> (raw)
In-Reply-To: <cover.1312852599.git.josh@linux.intel.com>
On Mon, 2011-08-08 at 18:18 -0700, Joshua Lock wrote:
> Here are some more bug fixes (and more on the way).
>
> Thanks,
> Joshua
>
> The following changes since commit 5cacdc4f1641eda1b5707c96f7c40924a9db6174:
>
> bb/cooker: mark parsed conf files as potential cache invalidators (2011-08-04 15:40:51 -0700)
>
> are available in the git repository at:
> git://github.com/incandescant/bitbake hob
> https://github.com/incandescant/bitbake/tree/hob
>
> Jessica Zhang (1):
> bb/ui/hob: Restore toolchain relevant preference settings for build
>
> Joshua Lock (3):
> bb/ui/crumbs/tasklistmodel: prevent hang when removing item
> bb/ui/hob: move some code around to avert a race
I've merged these three to master.
> bb/cooker: only emit ConfigFilePathFound for files which were parsed
This needs a little tweak.
Cheers,
Richard
prev parent reply other threads:[~2011-08-09 14:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-09 1:18 [PATCH 0/4] Bug fixes for hob Joshua Lock
2011-08-09 1:18 ` [PATCH 1/4] bb/ui/crumbs/tasklistmodel: prevent hang when removing item Joshua Lock
2011-08-09 1:18 ` [PATCH 2/4] bb/ui/hob: move some code around to avert a race Joshua Lock
2011-08-09 1:18 ` [PATCH 3/4] bb/cooker: only emit ConfigFilePathFound for files which were parsed Joshua Lock
2011-08-09 14:19 ` Richard Purdie
2011-08-09 1:18 ` [PATCH 4/4] bb/ui/hob: Restore toolchain relevant preference settings for build Joshua Lock
2011-08-09 14:20 ` 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=1312899633.14274.304.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=bitbake-devel@lists.openembedded.org \
--cc=josh@linux.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