From: "stomar (Marcus Stollsteimer)" Date: 2013-12-20T01:32:57+09:00 Subject: [ruby-core:59207] [ruby-trunk - Bug #9258] Fix bugreport URL in error.c Issue #9258 has been updated by stomar (Marcus Stollsteimer). I assume that bugs.r-l.org is the established and known site for reporting bugs. So now users that go there (to report bugs) should be pointed first to a HowTo on www.r-l.org and then come back to bugs.r-l.org to actually open an issue? That's also not very convincing to me. And I do not see any "backwards incompatibility" at all. The existing redirect from www.ruby-lang.org of course should be active as long as some officially supported branch points there. Note also that www.r-l.org/bugreport.html hadn't existed for I do not know how long, maybe since the big reworking of the site several years ago, where maybe it was overlooked that it is referenced from the Ruby source. IMO that's a good argument for pointing to a more general ressource like bugs.ruby-lang.org. Even more so since that same ressource is already linked to from many places in the code. Or alternatively error.c could just point to www.ruby-lang.org/. ---------------------------------------- Bug #9258: Fix bugreport URL in error.c https://bugs.ruby-lang.org/issues/9258#change-43764 Author: stomar (Marcus Stollsteimer) Status: Feedback Priority: Normal Assignee: naruse (Yui NARUSE) Category: Target version: next minor ruby -v: ruby 2.0.0p353 (2013-11-22 revision 43784) [i686-linux] Backport: 1.9.3: UNKNOWN, 2.0.0: UNKNOWN error.c refers to in REPORTBUG_MSG, which is only a redirect to . Instead it should refer to bugs.ruby-lang.org directly: * it's the "canonical" ressource for anything bug-related * it's already linked to from many other source files -- http://bugs.ruby-lang.org/