Archive of RubyForge sup-devel mailing list
 help / color / mirror / Atom feed
From: Vivien Didelot <vivien.didelot@gmail.com>
To: William@rubyforge.org, Morgan@rubyforge.org, wmorgan-sup@masanjin.net
Cc: Sup developer discussion <sup-devel@rubyforge.org>
Subject: [sup-devel] [PATCH] update Heliotrope client requirement
Date: Fri, 24 Jun 2011 01:49:26 -0400	[thread overview]
Message-ID: <1308894567-7174-1-git-send-email-vivien.didelot@gmail.com> (raw)

This patch is for the Turnsole project.

It comes with the
0001-put-the-heliotrope-client-into-the-Heliotrope-namesp.patch
patch for Heliotrope.

It updates the Heliotrope client requirement.

Signed-off-by: Vivien Didelot <vivien.didelot@gmail.com>
---
 lib/turnsole/client.rb |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/lib/turnsole/client.rb b/lib/turnsole/client.rb
index f651fe3..aaa402b 100644
--- a/lib/turnsole/client.rb
+++ b/lib/turnsole/client.rb
@@ -1,5 +1,5 @@
 require 'thread'
-require 'heliotrope-client'
+require 'heliotrope/client'
 
 ## all the methods here are asynchronous, except for ping!
 ## requests are queued and dispatched by the thread here. results are queued
@@ -10,7 +10,7 @@ class Client
 
   def initialize context, url
     @context = context
-    @client = HeliotropeClient.new url
+    @client = Heliotrope::Client.new url
     @client_mutex = Mutex.new # we sometimes access client from the main thread, for synchronous calls
     @q = Queue.new
   end
-- 
1.7.5.4

_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel


             reply	other threads:[~2011-06-24  6:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-24  5:49 Vivien Didelot [this message]
2011-06-24  5:49 ` [sup-devel] [PATCH] put the heliotrope client into the Heliotrope namespace Vivien Didelot

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=1308894567-7174-1-git-send-email-vivien.didelot@gmail.com \
    --to=vivien.didelot@gmail.com \
    --cc=Morgan@rubyforge.org \
    --cc=William@rubyforge.org \
    --cc=sup-devel@rubyforge.org \
    --cc=wmorgan-sup@masanjin.net \
    /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