From: Jonathan Lassoff <jof@thejof.com>
To: sup-talk <sup-talk@rubyforge.org>
Subject: [sup-talk] sup bug tracker down?
Date: Wed, 2 Jan 2013 12:24:43 -0800 [thread overview]
Message-ID: <CAHsqw9szovBD8_R+RBPXn66masg-i4RAH+s+k09mcrzc5EapqA@mail.gmail.com> (raw)
I hit a really unfortunate crash in my primary sup instance, and am
having trouble recovering from filesystem snapshot backups.
I went to go and submit a bug, but it seems that the bug tracker is
down. It still seems to be on wmorgan's domain. Should it still be
there? Maybe we could transition out to somewhere else?
I'll show the bug in another thread.
--j
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
reply other threads:[~2013-01-02 20:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAHsqw9szovBD8_R+RBPXn66masg-i4RAH+s+k09mcrzc5EapqA@mail.gmail.com \
--to=jof@thejof.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