From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Christopher Larson <kergoth@gmail.com>
Cc: Christopher Larson <chris_larson@mentor.com>,
bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH] cooker: now that we use a Pool, raise the exceptions
Date: Tue, 26 Feb 2013 07:29:09 -0800 [thread overview]
Message-ID: <1361892549.5119.4.camel@ted> (raw)
In-Reply-To: <1361818080-5758-1-git-send-email-kergoth@gmail.com>
On Mon, 2013-02-25 at 11:48 -0700, Christopher Larson wrote:
> From: Christopher Larson <chris_larson@mentor.com>
>
> Multiprocessing catches these and handles passing them between processes
> itself, we don't need to do it ourselves anymore.
>
> [YOCTO #3926]
>
> Signed-off-by: Christopher Larson <chris_larson@mentor.com>
> ---
> bitbake/lib/bb/cooker.py | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Makes sense, thanks (and merged)!
Richard
prev parent reply other threads:[~2013-02-26 15:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-25 18:48 [PATCH] cooker: now that we use a Pool, raise the exceptions Christopher Larson
2013-02-26 15:29 ` 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=1361892549.5119.4.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=bitbake-devel@lists.openembedded.org \
--cc=chris_larson@mentor.com \
--cc=kergoth@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox