From: jeff.covey@pobox.com (jeff covey)
Subject: [sup-talk] sorry about the non-responsiveness
Date: Sat, 30 Jun 2007 13:29:53 -0400 [thread overview]
Message-ID: <20070630172953.GA16906@mona.jeffcovey.net> (raw)
In-Reply-To: <1182964981-sup-6783@south>
it's ok with me -- aside from the various workarounds, sup has been working
fine for me until it blew up this morning. i think it's been a couple of
weeks, the longest i've been able to use it at a stretch! :)
unfortunately, every attempt i make now to build/rebuild the index
eventually leads to a ferret error, so i'm on a forced sup vacation.
thanks for the update!
--
jeff covey
http://jeffcovey.net/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 229 bytes
Desc: Digital signature
Url : http://rubyforge.org/pipermail/sup-talk/attachments/20070630/8d7b3801/attachment.bin
prev parent reply other threads:[~2007-06-30 17:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-27 17:25 William Morgan
2007-06-30 17:29 ` jeff covey [this message]
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=20070630172953.GA16906@mona.jeffcovey.net \
--to=jeff.covey@pobox.com \
/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