Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: Michael Stapelberg <michael+sup@stapelberg.de>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Sup bug tracker down for >week?
Date: Mon, 21 Mar 2011 16:20:51 +0100	[thread overview]
Message-ID: <1300720800-sup-7933@midna.zekjur.net> (raw)
In-Reply-To: <AANLkTinMGNG353_ocTwiN+W4ATs9yQR+FJgyOv2fkpdJ@mail.gmail.com>

Hi Shadowfirebird,

Excerpts from Shadowfirebird's message of 2011-03-21 10:53:12 +0100:
> Does everyone else see the sup bug tracker as down?  It seems to have been
> down for at least a week.

William has taken it down due to the amount of spambot traffic killing his
server, see his message from 2011-01-10 with Message ID
1294636135-sup-6653@masanjin.net.

Best regards,
Michael
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk


  reply	other threads:[~2011-03-21 15:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-21  9:53 Shadowfirebird
2011-03-21 15:20 ` Michael Stapelberg [this message]
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=1300720800-sup-7933@midna.zekjur.net \
    --to=michael+sup@stapelberg.de \
    --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