From: chrisw@rice.edu (Christopher Warrington)
Subject: [sup-talk] bug: reproducable Sup crash, ferret-less rewrite?
Date: Fri, 31 Oct 2008 22:16:39 -0500 [thread overview]
Message-ID: <C5313447.2C02%chrisw@rice.edu> (raw)
In-Reply-To: <YILM7EO5.1225497165.2060790.tpo2@192.168.3.7>
"Tomas Pospisek ML" <tpo2 at sourcepole.ch> @ 2008-10-31 6:52 PM:
> I can not find any trace of the latter, i.e. Sup's source code
> repository at Gitorious [3] doesn't show any ferret amputation. Are
> you, William Morgan working on a Sup version that doesn't show that
> supposedly ferret induced crashiness? Possibly your "private" branch
> is not ready yet and not accessible?
See these blog posts about "Sup: The Server!"
http://all-thing.net/search/label/sup
--
Christopher Warrington <chrisw at rice.edu>
Jones College
next prev parent reply other threads:[~2008-11-01 3:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-31 23:52 Tomas Pospisek ML
2008-11-01 3:16 ` Christopher Warrington [this message]
2008-11-01 22:13 ` Tomas Pospisek ML
2008-11-02 18:30 ` William Morgan
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=C5313447.2C02%chrisw@rice.edu \
--to=chrisw@rice.edu \
/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