Where do I report Ruby bugs? I checked the FAQ for this news group,
and did not see anything. Is rubyforge.org the correct place?
Thanks in advance,
Michael Schonberg
Yup. When you post a bug here:
http://rubyforge.org/tracker/?atid=1698&group_id=426&func=browse
an email is automatically sent to the ruby-core mailing list with a link
to your bug post.
Yours,
Tom
···
On Wed, 2005-04-27 at 05:09 +0900, Michael Schonberg wrote:
Where do I report Ruby bugs? I checked the FAQ for this news group,
and did not see anything. Is rubyforge.org the correct place?
Michael Schonberg wrote:
Where do I report Ruby bugs? I checked the FAQ for this news group,
and did not see anything. Is rubyforge.org the correct place?Thanks in advance,
Michael Schonberg
One place is http://rubyforge.org/
In the upper-right corner of the page, under "Support/Links" is the link "Report a Ruby Bug", which takes you to
http://rubyforge.org/tracker/?atid=1698&group_id=426&func=browse
Yup. When you post a bug here:
http://rubyforge.org/tracker/?atid=1698&group_id=426&func=browse
an email is automatically sent to the ruby-core mailing list with a link
to your bug post.
Of course, if you don't receive a followup, you may want to subscribe to
ruby-core:
http://www.ruby-lang.org/en/20020104.html
and see if the issue has been resolved or is pending something or
whatever...
Yours,
Tom
Thanks,
-Mike
···
On Wed, 27 Apr 2005 05:19:05 +0900, Tom Copeland wrote:
[quoted text muted]
Of course, if you don't receive a followup, you may want to subscribe to
ruby-core:http://www.ruby-lang.org/en/20020104.html
and see if the issue has been resolved or is pending something or
whatever...Yours,
Tom
And don't forget to demand an apology.
martin
···
Tom Copeland <tom@infoether.com> wrote:
> Yup. When you post a bug here:
>
> http://rubyforge.org/tracker/?atid=1698&group_id=426&func=browse
>
> an email is automatically sent to the ruby-core mailing list with a link
> to your bug post.Of course, if you don't receive a followup, you may want to subscribe to
ruby-core:http://www.ruby-lang.org/en/20020104.html
and see if the issue has been resolved or is pending something or
whatever...