From: Joshua Lock <josh@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/1] Enhance network connectivity sanity check
Date: Thu, 25 Aug 2011 08:29:29 -0700 [thread overview]
Message-ID: <cover.1314286007.git.josh@linux.intel.com> (raw)
The patch header says it all, I've switched to using the checkstatus API of
fetch2 to implement the network connectivity check.
This adds a requirement for BitBake master as of yesterday if you want to
sanity check a gainst git uri's.
The following changes since commit 445d6426197579a9c0317498cc6919bb63e7f726:
meta-toolchain/environment: Collected site config files in runtime. (2011-08-24 19:26:01 -0700)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib josh/connection-test
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=josh/connection-test
Joshua Lock (1):
classes/sanity: enhance the network connectivity test
meta/classes/sanity.bbclass | 14 ++------------
1 files changed, 2 insertions(+), 12 deletions(-)
--
1.7.6
next reply other threads:[~2011-08-25 15:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-25 15:29 Joshua Lock [this message]
2011-08-25 15:29 ` [PATCH 1/1] classes/sanity: enhance the network connectivity test Joshua Lock
2011-08-25 15:50 ` Richard Purdie
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.1314286007.git.josh@linux.intel.com \
--to=josh@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