From: Rich Pixley <rich.pixley@palm.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: SetScene tasks hang forever?
Date: Wed, 09 May 2012 17:00:52 -0700 [thread overview]
Message-ID: <4FAB0534.5070205@palm.com> (raw)
In-Reply-To: <1336606329.2494.105.camel@ted>
On 5/9/12 16:32 , Richard Purdie wrote:
> On Wed, 2012-05-09 at 16:20 -0700, Rich Pixley wrote:
>> My rebuild completed in 5 seconds.
>>
>> Thank you very much!
>>
>> I'd rather not fork bitbake locally. Can I expect this patch to show up
>> in git://git.openembedded.org/bitbake sometime soon?
> Yes, I just wanted to confirm we were fixing the right problem...
>
> I'll post it to the bitbake list and merge in a day or two assuming no
> negative feedback.
I'm running more thorough tests as I type.
> I still wonder if that stamp mode is useful but that is a different
> discussion.
If I'm understanding your other message, then no, it's probably not.
My only concern is that in the A depends on B depends on C case,
changing C forces a rebuild of A. I don't really care which mechanism
makes that happen.
--rich
prev parent reply other threads:[~2012-05-10 0:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-02 18:21 SetScene tasks hang forever? Rich Pixley
2012-05-02 18:40 ` Mark Hatle
2012-05-02 19:16 ` Rich Pixley
2012-05-02 19:40 ` Mark Hatle
2012-05-02 19:45 ` Rich Pixley
2012-05-02 19:48 ` Mark Hatle
2012-05-02 23:06 ` Richard Purdie
2012-05-06 17:36 ` Rich Pixley
2012-05-07 16:38 ` Rich Pixley
2012-05-08 12:34 ` Richard Purdie
2012-05-09 17:51 ` Rich Pixley
2012-05-09 19:52 ` Richard Purdie
2012-05-09 23:04 ` Rich Pixley
2012-05-09 23:26 ` Richard Purdie
2012-05-10 0:03 ` Rich Pixley
2012-05-09 20:32 ` Richard Purdie
2012-05-09 23:20 ` Rich Pixley
2012-05-09 23:32 ` Richard Purdie
2012-05-10 0:00 ` Rich Pixley [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=4FAB0534.5070205@palm.com \
--to=rich.pixley@palm.com \
--cc=openembedded-core@lists.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.