From: ecoffey@gmail.com (Eoin Coffey)
Subject: [sup-talk] Sup initalize setup crash
Date: Thu, 3 Jul 2008 17:08:27 -0600 [thread overview]
Message-ID: <2d88cc360807031608i44d90bf1o402a0666a737e8d8@mail.gmail.com> (raw)
Just finished sup-config and configured for secure imap (its a gmail
account).
-Eoin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20080703/34aa0c0e/attachment.html>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: sup-exception-log.txt
URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20080703/34aa0c0e/attachment.txt>
next reply other threads:[~2008-07-03 23:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-03 23:08 Eoin Coffey [this message]
2008-07-04 0:55 ` wmorgan-sup
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=2d88cc360807031608i44d90bf1o402a0666a737e8d8@mail.gmail.com \
--to=ecoffey@gmail.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