From: Jeremy Puhlman <jpuhlman@mvista.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: bitbake-devel <bitbake-devel@lists.openembedded.org>
Subject: Re: Couple of nasty bitbake issues
Date: Thu, 16 Jun 2011 07:45:53 -0700 [thread overview]
Message-ID: <4DFA1721.70701@mvista.com> (raw)
In-Reply-To: <1308232450.15712.436.camel@rex>
> http://git.yoctoproject.org/cgit.cgi/poky-contrib/commit/?h=rpurdie/ml&id=a3a130b3c6ca760066ca830eb46fa472ecb84c88
I did a quick build with this and it seems to cover the issue I
mentioned this morning. Ill kick off a more robust build, is there
anything I should be watching out for?
--
Jeremy Puhlman
Montavista Sofware, LLC.
next prev parent reply other threads:[~2011-06-16 14:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-16 13:54 Couple of nasty bitbake issues Richard Purdie
2011-06-16 14:45 ` Jeremy Puhlman [this message]
2011-06-16 23:35 ` Khem Raj
2011-06-17 1:59 ` Khem Raj
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=4DFA1721.70701@mvista.com \
--to=jpuhlman@mvista.com \
--cc=bitbake-devel@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 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.