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] Hob bug fixes
Date: Sun, 25 Sep 2011 16:26:43 +0100 [thread overview]
Message-ID: <1316964411.8185.20.camel@ted> (raw)
In-Reply-To: <cover.1316809959.git.josh@linux.intel.com>
On Fri, 2011-09-23 at 13:34 -0700, Joshua Lock wrote:
> This series includes a few fixes found whilst debugging and fixing
> Yocto bug #1521
> http://bugzilla.yoctoproject.org/show_bug.cgi?id=1521
>
> Richard, please consider these for Yocto 1.1
>
> Regards,
> Joshua
>
> The following changes since commit 623e9c7f7a9cf12b8c81c26cc608990682a601dd:
>
> Fix mercurial fetcher in fetch2 (2011-09-21 14:07:14 +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/hobeventhandler: move remaining getVariable calls to init
> ui/crumbs/hobeventhandler: fix variable name typo
> hob: fix building with current selections after reparse
Merged to master, thanks.
Richard
next prev parent reply other threads:[~2011-09-25 15:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-23 20:34 [PATCH 0/3] Hob bug fixes Joshua Lock
2011-09-23 20:34 ` [PATCH 1/3] ui/crumbs/hobeventhandler: move remaining getVariable calls to init Joshua Lock
2011-09-23 20:34 ` [PATCH 2/3] ui/crumbs/hobeventhandler: fix variable name typo Joshua Lock
2011-09-23 20:34 ` [PATCH 3/3] hob: fix building with current selections after reparse Joshua Lock
2011-09-25 15:26 ` Richard Purdie [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-06-01 10:36 [PATCH 0/3] Hob: bug fixes Liming An
2012-06-08 11:01 ` 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=1316964411.8185.20.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