From: Jason Petsod <jason@petsod.org>
To: sup-talk <sup-talk@rubyforge.org>
Subject: [sup-talk] sup web interface
Date: Fri, 30 Apr 2010 00:43:24 -0500 [thread overview]
Message-ID: <1272606137-sup-842@acheron.quadco.net> (raw)
Hi,
Is there still interest in a web interface for sup? There appear to be
previous discussions on it [1][2], but it doesn't seem like anything
conclusive was created.
If there is interest, is there a specific web framework (or no framework)
the community would prefer? I might have some time this weekend to cobble
something together...
-Jason
[1] http://www.mail-archive.com/sup-talk@rubyforge.org/msg01536.html
[2] http://www.mail-archive.com/sup-talk@rubyforge.org/msg03192.html
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next reply other threads:[~2010-04-30 6:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-30 5:43 Jason Petsod [this message]
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
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=1272606137-sup-842@acheron.quadco.net \
--to=jason@petsod.org \
--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