From: Marc Weber <marco-oweber@gmx.de>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] problem starting sup
Date: Thu, 27 Jan 2011 01:24:24 +0100 [thread overview]
Message-ID: <1296087829-sup-1828@localhost.localdomain> (raw)
In-Reply-To: <AANLkTi=ZX0cT-fiT7DeETx7wbO77wZeLJk86_zhbkqGF@mail.gmail.com>
Excerpts from Hamish D's message of Thu Jan 27 00:59:24 +0100 2011:
> Any ideas?
No, but you should talk about ruby --version output
and the git version of sup you're using?
Marc Weber
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2011-01-27 0:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-26 23:59 Hamish D
2011-01-27 0:24 ` Marc Weber [this message]
2011-01-27 1:57 ` William Morgan
2011-01-30 23:07 ` Hamish D
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=1296087829-sup-1828@localhost.localdomain \
--to=marco-oweber@gmx.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