From: dfortunato@gmail.com (David Fortunato)
Subject: [sup-talk] crash with 'Too many clauses'
Date: Thu, 17 Jan 2008 18:56:37 -0800 (PST) [thread overview]
Message-ID: <14944700.post@talk.nabble.com> (raw)
In-Reply-To: <12ACF456-3FEA-4BC0-B4AD-BD918B80C095@gmail.com>
Please ignore the previous email. I hadn't read HACKING yet, and it was
running the 0.3 gem. Everything is working great.
--
View this message in context: http://www.nabble.com/crash-with-%27Too-many-clauses%27-tp14939928p14944700.html
Sent from the SUP Talk mailing list archive at Nabble.com.
prev parent reply other threads:[~2008-01-18 2:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-18 0:11 David Fortunato
2008-01-18 2:56 ` David Fortunato [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=14944700.post@talk.nabble.com \
--to=dfortunato@gmail.com \
/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