From: William Morgan <wmorgan-sup@masanjin.net>
To: Sup-talk mailing list <sup-talk@rubyforge.org>
Subject: [sup-talk] sup bug tracker
Date: Fri, 06 Nov 2009 08:33:03 -0800 [thread overview]
Message-ID: <1257524700-sup-9112@masanjin.net> (raw)
Hi all,
I've put a slightly modified Roundup installation here for tracking Sup
bugs:
http://masanjin.net/sup-bugs/
Please use this to submit your bug reports and feature requests. If you
have existing bug reports or feature requests and you don't want to rely
on my faulty memory any more, feel free to resubmit them here.
You should be able to create new issues without having to register.
However, if you want to receive email about an issue when updates
happen, you will have to register. Sorry! On the plus side, registration
is super quick because I've disabled the email confirmation step.
If anyone has written Roundup detectors in the past, let me know. There
are a couple things I'd like to tweak.
I'm going to point the 0.9.1 crash message there too.
--
William <wmorgan-sup@masanjin.net>
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next reply other threads:[~2009-11-06 16:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-06 16:33 William Morgan [this message]
2009-11-07 11:15 ` Tero Tilus
2009-11-07 16:32 ` William Morgan
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=1257524700-sup-9112@masanjin.net \
--to=wmorgan-sup@masanjin.net \
--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