From: Rich Pixley <rich.pixley@palm.com>
To: "openembedded-devel@openembedded.org"
<openembedded-devel@openembedded.org>
Subject: Re: bitbake vs incremental builds
Date: Mon, 23 Jun 2008 11:23:05 -0700 [thread overview]
Message-ID: <485FEA09.2010507@palm.com> (raw)
In-Reply-To: <1213955086.5049.7.camel@dax.rpnet.com>
Richard Purdie wrote:
> If you can show a more specific problem perhaps we can help but at the
> moment you're tying our hands :(.
And unfortunately, it must stay that way for a while longer.
I'll try to get myself up to speed on using top of tree OE this week.
That portion of our project was before my time so it'll be a learning curve.
--rich
next prev parent reply other threads:[~2008-06-23 18:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-18 22:40 bitbake vs incremental builds Rich Pixley
2008-06-19 7:58 ` Richard Purdie
2008-06-19 16:57 ` K. Richard Pixley
2008-06-19 17:30 ` Cliff Brake
2008-06-20 1:03 ` Rich Pixley
2008-06-20 9:44 ` Richard Purdie
2008-06-23 18:23 ` Rich Pixley [this message]
2008-06-25 22:28 ` Rich Pixley
2008-06-26 20:53 ` rebuild confusion Rich Pixley
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=485FEA09.2010507@palm.com \
--to=rich.pixley@palm.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.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.