From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Joshua Lock <josh@linux.intel.com>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH 0/3] Various hob fixes
Date: Tue, 20 Sep 2011 22:16:42 +0100 [thread overview]
Message-ID: <1316553408.14488.78.camel@ted> (raw)
In-Reply-To: <cover.1316530819.git.josh@linux.intel.com>
On Tue, 2011-09-20 at 08:01 -0700, Joshua Lock wrote:
> 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
Merged to master, thanks.
Richard
prev parent reply other threads:[~2011-09-20 21:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-20 15:01 [PATCH 0/3] Various hob fixes Joshua Lock
2011-09-20 15:01 ` [PATCH 1/3] ui/crumbs/hobprefs: re-enable reloading of data after prefs changes Joshua Lock
2011-09-20 15:01 ` [PATCH 2/3] hob: fix build again when building packages only Joshua Lock
2011-09-20 15:01 ` [PATCH 3/3] hob: enable package only builds even if an image has been built Joshua Lock
2011-09-20 21:16 ` 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=1316553408.14488.78.camel@ted \
--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