From: Tero Tilus <tero@tilus.net>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] sup bug tracker
Date: Sat, 07 Nov 2009 13:15:56 +0200 [thread overview]
Message-ID: <1257591624-sup-8158@tilus.net> (raw)
In-Reply-To: <1257524700-sup-9112@masanjin.net>
William Morgan, 2009-11-06 18:33:
> 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.
What should be the policy with issues are reported/discussed on irc or
mailinglist but are not reported to tracker? Should The Sup Issues
Task Force(TM) ;) report them to tracker or try to push the original
reporter to do it?
Should we (The SITF) skim mailinglist archives and transfer reported
unfixed bugs (with links to archives) to tracker?
> I'm going to point the 0.9.1 crash message there too.
Sup home http://sup.rubyforge.org/ is not yet pointing there.
--
Tero Tilus ## 050 3635 235 ## http://tero.tilus.net/
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2009-11-07 11:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-06 16:33 William Morgan
2009-11-07 11:15 ` Tero Tilus [this message]
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=1257591624-sup-8158@tilus.net \
--to=tero@tilus.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