From: Shadowfirebird <shadowfirebird@gmail.com>
To: sup-talk <sup-talk@rubyforge.org>
Subject: [sup-talk] Sup bug tracker down for >week?
Date: Mon, 21 Mar 2011 09:53:12 +0000 [thread overview]
Message-ID: <AANLkTinMGNG353_ocTwiN+W4ATs9yQR+FJgyOv2fkpdJ@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 403 bytes --]
Does everyone else see the sup bug tracker as down? It seems to have been
down for at least a week.
My Sup has crashed, no-one on this list seems to be able to help me and the
bug tracker is down. Much as I like Sup, I think this might be game over as
far as I'm concerned...
--
What a tangled web we weave / Go 'round with circumstance / Someone show me
how to tell / The dancer from the dance...
[-- Attachment #1.2: Type: text/html, Size: 445 bytes --]
[-- Attachment #2: Type: text/plain, Size: 140 bytes --]
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next reply other threads:[~2011-03-21 10:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-21 9:53 Shadowfirebird [this message]
2011-03-21 15:20 ` Michael Stapelberg
2011-03-21 15:31 ` Amadeusz Żołnowski
2011-03-22 16:47 ` Shadowfirebird
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=AANLkTinMGNG353_ocTwiN+W4ATs9yQR+FJgyOv2fkpdJ@mail.gmail.com \
--to=shadowfirebird@gmail.com \
--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