Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: Moritz Wilhelmy <moritz+sup@wzff.de>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] sup and ruby 1.9
Date: Tue, 26 Oct 2010 12:45:02 +0200	[thread overview]
Message-ID: <1288089771-sup-406@niflheimr> (raw)
In-Reply-To: <1288087383-sup-6381@eris>

> 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?

I myself have 1.8 installed in /opt and use it for running sup. My distro
(arch) likes upgrading to beta-versions way too much, and I want my mailclient
to be stable ;)
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk


      reply	other threads:[~2010-10-26 11:19 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
2010-10-26 10:04 ` Philipp Überbacher
2010-10-26 10:45   ` Moritz Wilhelmy [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=1288089771-sup-406@niflheimr \
    --to=moritz+sup@wzff.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