From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Robert Yang <liezhi.yang@windriver.com>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: [RFC PATCH 1/1] Fix bitbake-runtask
Date: Fri, 25 Nov 2011 11:36:33 +0000 [thread overview]
Message-ID: <1322220993.10928.63.camel@ted> (raw)
In-Reply-To: <4ECF5AB0.5020204@windriver.com>
On Fri, 2011-11-25 at 17:06 +0800, Robert Yang wrote:
> Thank you very much, this is pretty good, I've tested it, it worked
> well. What shall I do for it then? Should I send the pull request or
> you will merge it from you branch?
I've merged this patch into Poky, splitting out the siggen change into a
separate commit which I also pushed upstream. bitbake-runtask isn't in
upstream bitbake, it was one of the last remaining differences between
bitbake in poky and the upstream.
Now the script works, we can likely get this into upstream and get that
difference resolved once and for all.
Cheers,
Richard
prev parent reply other threads:[~2011-11-25 11:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-15 13:45 [RFC PATCH 0/1] Fix bitbake-runtask Robert Yang
2011-11-15 13:45 ` [RFC PATCH 1/1] " Robert Yang
2011-11-24 2:06 ` Robert Yang
2011-11-24 13:03 ` Richard Purdie
2011-11-25 9:06 ` Robert Yang
2011-11-25 11:36 ` Richard Purdie [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=1322220993.10928.63.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=bitbake-devel@lists.openembedded.org \
--cc=liezhi.yang@windriver.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 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.