From: Christopher Larson <kergoth@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: Christopher Larson <chris_larson@mentor.com>
Subject: [PATCH 0/2] Resolve parsing hang issues
Date: Tue, 7 Feb 2012 22:13:43 -0600 [thread overview]
Message-ID: <cover.1328674343.git.chris_larson@mentor.com> (raw)
From: Christopher Larson <chris_larson@mentor.com>
*** BLURB HERE ***
The following changes since commit db689a99beffea1a285cdfc74a58fe73f1666987:
Revert the switch to futures for now (2012-02-03 08:12:56 -0700)
are available in the git repository at:
git://github.com/kergoth/bitbake.git hang-issue-fix
https://github.com/kergoth/bitbake/tree/hang-issue-fix
Christopher Larson (2):
cooker: roll our own process pool
knotty: shut down more cleanly
lib/bb/cooker.py | 155 ++++++++++++++++++++++++++++++++++++++++++---------
lib/bb/ui/knotty.py | 15 ++---
2 files changed, 136 insertions(+), 34 deletions(-)
--
1.7.7
next reply other threads:[~2012-02-08 4:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-08 4:13 Christopher Larson [this message]
2012-02-08 4:13 ` [PATCH 1/2] cooker: roll our own process pool Christopher Larson
2012-02-08 4:13 ` [PATCH 2/2] knotty: shut down more cleanly Christopher Larson
2012-02-08 4:14 ` [PATCH 0/2] Resolve parsing hang issues Chris Larson
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=cover.1328674343.git.chris_larson@mentor.com \
--to=kergoth@gmail.com \
--cc=chris_larson@mentor.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox