From: "Aníbal Limón" <anibal.limon@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH] classes/sstate.bbclass: Improve checkstatus using connection cache.
Date: Tue, 23 Jun 2015 15:02:40 -0500 [thread overview]
Message-ID: <1435089761-27337-1-git-send-email-anibal.limon@linux.intel.com> (raw)
This patch depends on changes did in bitbake [1] and oe/utils.py [2], don't merge
before it.
For complete review exist an integration branch at,
http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=alimon/fetch2-wget-checkstatus
[1] http://lists.openembedded.org/pipermail/bitbake-devel/2015-June/005912.html
[2] http://lists.openembedded.org/pipermail/openembedded-core/2015-June/106430.html
Aníbal Limón (1):
classes/sstate.bbclass: Improve checkstatus using connection cache.
meta/classes/sstate.bbclass | 19 +++++++++++++++++--
1 file changed, 17 insertions(+), 2 deletions(-)
--
1.9.1
next reply other threads:[~2015-06-23 20:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-23 20:02 Aníbal Limón [this message]
2015-06-23 20:02 ` [PATCH] classes/sstate.bbclass: Improve checkstatus using connection cache Aníbal Limón
2015-06-23 21:42 ` Christopher Larson
2015-06-23 22:51 ` Aníbal Limón
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=1435089761-27337-1-git-send-email-anibal.limon@linux.intel.com \
--to=anibal.limon@linux.intel.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