From: Andreas Happe <andreashappe@snikt.net>
To: sup-talk@rubyforge.org
Subject: Re: [sup-talk] sup web interface
Date: Fri, 4 Jun 2010 12:01:08 +0000 (UTC) [thread overview]
Message-ID: <loom.20100604T135436-725@post.gmane.org> (raw)
In-Reply-To: <1275577785-sup-679@zyrg.net>
Rich Lane <rlane <at> club.cc.cmu.edu> writes:
> Excerpts from Andreas Happe's message of 2010-06-03 09:11:31 -0400:
> > I won't start it (as I don't have nearly enough time on my hand), but might
> > contribute -- just put a rough (but working) prototype on github.
>
> Link?
To github[0]? My last sentence could have been clearer: I haven't put anything
sup-related up on github, but if someone starts with a rough, but working,
prototype I could help out.
cheers, Andreas
[0] http://www.github.org
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2010-06-04 12:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-30 5:43 Jason Petsod
2010-04-30 14:17 ` Nicholas Bergson-Shilcock
2010-04-30 14:57 ` Jon Dugan
2010-04-30 23:13 ` Rich Lane
2010-06-03 13:11 ` Andreas Happe
2010-06-03 15:16 ` Rich Lane
2010-06-04 12:01 ` Andreas Happe [this message]
2010-06-04 15:59 ` Jason Petsod
2010-06-05 3:55 ` Rich Lane
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=loom.20100604T135436-725@post.gmane.org \
--to=andreashappe@snikt.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