Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] classes/sanity: enhance the network connectivity test
Date: Thu, 25 Aug 2011 08:50:19 -0700	[thread overview]
Message-ID: <1314287419.5939.199.camel@rex> (raw)
In-Reply-To: <452876f08ee6516713d5a7198e8589953cd35f4b.1314286007.git.josh@linux.intel.com>

On Thu, 2011-08-25 at 08:29 -0700, Joshua Lock wrote:
> Switch to use the checkstatus fetcher API for the network connectivity test,
> this has several advantages:
> * we no longer print any messages to the console whilst the check is
> being run
> * we don't actually download anything, removing the need for tidy up and
> making the code more concise
> 
> Signed-off-by: Joshua Lock <josh@linux.intel.com>

Merged to master, thanks.

Richard




      reply	other threads:[~2011-08-25 15:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-25 15:29 [PATCH 0/1] Enhance network connectivity sanity check Joshua Lock
2011-08-25 15:29 ` [PATCH 1/1] classes/sanity: enhance the network connectivity test Joshua Lock
2011-08-25 15:50   ` 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=1314287419.5939.199.camel@rex \
    --to=richard.purdie@linuxfoundation.org \
    --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