From: Michael Stapelberg <michael+sup@stapelberg.de>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] sup and ruby 1.9
Date: Tue, 26 Oct 2010 08:06:25 +0200 [thread overview]
Message-ID: <1288073067-sup-885@midna.zekjur.net> (raw)
In-Reply-To: <AANLkTinRQ9A+8630CnUKam1h2X5o_N_n9e6GgY_weLkQ@mail.gmail.com>
Hi Hamish,
Excerpts from Hamish D's message of 2010-10-26 01:06:51 +0200:
> I'm wondering what the status of sup and ruby 1.9 is. Is it stable and
> no more buggy than on ruby 1.8? Is it significantly faster than on
> ruby 1.8?
It works just fine. I run it since a few months without any problems. For ruby
1.9.2, you need some patches:
http://rubyforge.org/pipermail/sup-talk/2010-September/004223.html
> If I did go for the change, can I switch back and forth between ruby
> versions? Should I reinstall all the gems that sup depends on?
Yes, you need to install all gems.
Best regards,
Michael
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2010-10-26 11:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-25 23:06 Hamish D
2010-10-26 6:06 ` Michael Stapelberg [this message]
2010-10-26 10:04 ` Philipp Überbacher
2010-10-26 10:45 ` Moritz Wilhelmy
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=1288073067-sup-885@midna.zekjur.net \
--to=michael+sup@stapelberg.de \
--cc=sup-talk@rubyforge.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