Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: William Morgan <wmorgan-sup@masanjin.net>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Ruby 1.9 status?
Date: Mon, 12 Oct 2009 05:14:42 -0700	[thread overview]
Message-ID: <1255349584-sup-5924@masanjin.net> (raw)
In-Reply-To: <1255029826-sup-8182@peray>

Reformatted excerpts from Nicolas Pouillard's message of 2009-10-08:
> I would like to know what is the sup status w.r.t ruby 1.9?

The code is syntactically ready for 1.9. There's a Ferret 1.9 gem as of
recently, which you can try. Someone wrote a blog post here:

http://trickyco.de/2009/09/24/installing-the-sup-mua-on-64bit-arch-linux

And made some patches, which I haven't had a chance to review yet.

At some point I tried Xapian with 1.9 and ran into some weird errors. If
you search the mailing list, you should find it.
-- 
William <wmorgan-sup@masanjin.net>
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk


      reply	other threads:[~2009-10-12 12:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-08 19:24 Nicolas Pouillard
2009-10-12 12:14 ` William Morgan [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=1255349584-sup-5924@masanjin.net \
    --to=wmorgan-sup@masanjin.net \
    --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