Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] Can sup only "save threads" on exit??
Date: Thu, 06 Nov 2008 08:18:46 -0800	[thread overview]
Message-ID: <1225987338-sup-6300@entry> (raw)
In-Reply-To: <1225982260-sup-3050@sgoldmanlinux.tower-research.com>

Reformatted excerpts from Steve Goldman's message of 2008-11-06:
> Point me to a beginning ruby tutorial!  I've never contributed to
> anything open source before.  So exciting.

There are a couple Ruby for beginners tutorials:
- http://pine.fm/LearnToProgram/?Chapter=01,
- http://poignantguide.net/ruby/ (best read while high),
- http://tryruby.hobix.com/

But you might be better of with Ruby for Java programmers stuff:
- http://onestepback.org/articles/10things/
- http://www.jroller.com/obie/entry/ruby_primer_for_java_programmers

etc.

You'll also have to know git to contribute to Sup. See
http://sup.rubyforge.org/wiki/wiki.pl?Contributing.
-- 
William <wmorgan-sup at masanjin.net>


  reply	other threads:[~2008-11-06 16:18 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-04 22:55 Steve Goldman
2008-11-05  0:36 ` John Bent
2008-11-05 13:06   ` Nicolas Pouillard
2008-11-06 16:19     ` William Morgan
2008-11-07 14:18       ` Nicolas Pouillard
2008-11-10  4:49         ` William Morgan
2008-11-05 14:34   ` Steve Goldman
2008-11-05 17:59     ` William Morgan
2008-11-06 14:38       ` Steve Goldman
2008-11-06 16:18         ` William Morgan [this message]
2008-11-06 14:40     ` Nicolas Pouillard
2008-11-06 15:00       ` [sup-talk] [PATCH] save contacts.txt on '$' Nicolas Pouillard
2008-11-10  4:51         ` William Morgan
2008-11-06 22:35     ` [sup-talk] Can sup only "save threads" on exit?? William Morgan
2008-11-07 17:13       ` Mike Stipicevic

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=1225987338-sup-6300@entry \
    --to=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