From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [CONSOLIDATED PULL 00/44] Pre-M2 Patches and Updates
Date: Tue, 02 Jul 2013 22:53:34 +0100 [thread overview]
Message-ID: <1543512.IOqlhupRf5@helios> (raw)
In-Reply-To: <1372800607.25291.43.camel@ted>
On Tuesday 02 July 2013 22:30:07 Richard Purdie wrote:
> On Tue, 2013-07-02 at 08:09 -0700, Saul Wold wrote:
> > We have reviewed and built and done some testing on the following
> > patch set. Paul worked on fixing a number of the Autobuilder
> > failures from MUT.
>
> Thanks, I merged these.
>
> > Paul has a bitbake patch for M2 also
>
> Ok, but where do I find it? Can't see a patch from him on the bitbake
> mailing list?
It was Cristiana's hob patch. I have pushed this to the paule/bitbake branch
on poky-contrib, sorry for not sending you this previously.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
prev parent reply other threads:[~2013-07-02 21:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-02 15:09 [CONSOLIDATED PULL 00/44] Pre-M2 Patches and Updates Saul Wold
2013-07-02 21:30 ` Richard Purdie
2013-07-02 21:53 ` Paul Eggleton [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=1543512.IOqlhupRf5@helios \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
/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