From: kevin.mark@verizon.net (Kevin Mark)
Subject: [sup-talk] wup
Date: Thu, 8 Nov 2007 03:49:10 -0500 [thread overview]
Message-ID: <20071108084910.GH13064@horacrux> (raw)
In-Reply-To: <1194487545-sup-8478@south>
On Wed, Nov 07, 2007 at 06:08:00PM -0800, William Morgan wrote:
> Hi Suppers,
>
> My friend Leslie has hacked together "wup", a web interface on top of
> Sup: http://jinsync.com/?q=node/16.
>
> 75 lines of code gets you quite a lot!
>
This is what make FLOSS great! Release early, Release often. And allow
folks to build on it. Cool.
-K
--
| .''`. == Debian GNU/Linux == | my web site: |
| : :' : The Universal |mysite.verizon.net/kevin.mark/|
| `. `' Operating System | go to counter.li.org and |
| `- http://www.debian.org/ | be counted! #238656 |
| my keyserver: subkeys.pgp.net | my NPO: cfsg.org |
|join the new debian-community.org to help Debian! |
|_______ Unless I ask to be CCd, assume I am subscribed _______|
next prev parent reply other threads:[~2007-11-08 8:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-08 2:08 William Morgan
2007-11-08 8:49 ` Kevin Mark [this message]
2007-11-08 14:49 ` nicholas a. evans
2008-02-01 8:49 ` Manish Sapariya
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=20071108084910.GH13064@horacrux \
--to=kevin.mark@verizon.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