Bug #9258


Fix bugreport URL in error.c

Added by stomar (Marcus Stollsteimer) over 8 years ago. Updated over 4 years ago.

Target version:
ruby -v:
ruby 2.0.0p353 (2013-11-22 revision 43784) [i686-linux]


error.c refers to <> in REPORTBUG_MSG, which is only a redirect to <>. Instead it should refer to directly:

  • it's the "canonical" ressource for anything bug-related
  • it's already linked to from many other source files


bugreport.patch (442 Bytes) bugreport.patch stomar (Marcus Stollsteimer), 12/18/2013 10:57 PM

Related issues 1 (0 open1 closed)

Is duplicate of Ruby master - Feature #8931: Update URL in REPORTBUG_MSGRejected09/20/2013Actions

Updated by zzak (Zachary Scott) over 8 years ago

  • Target version changed from 2.1.0 to 2.6

We should discuss this for after 2.1.0 is released, it's too soon now

Updated by naruse (Yui NARUSE) over 8 years ago

  • Status changed from Open to Rejected

Changing error.c is not acceptable.
"" is not the best place for people who just report the bug.
It also includes joining development, request a feature.

Changing the content of is acceptable.

Updated by stomar (Marcus Stollsteimer) over 8 years ago

@naruse (Yui NARUSE)

I agree that "" is not only a place to report bugs.

But it has all the relevant information on bug reporting right there on the root page ("How to Report a Bug"),
and it will always need to have that information, or it stops being

Why use a second ressource that doesn't even exist?

It's already referenced in many places in the code, so in case you would want to move it to another site there would need to be fixes in the code anyway.

Updated by zzak (Zachary Scott) over 8 years ago

  • Status changed from Rejected to Feedback
  • Assignee set to naruse (Yui NARUSE)

I'm not sure why it would be unacceptable for next minor? We should be allowed to make backwards incompatible changes after 2.1 is released for next minor.

Anyways, I agree maybe it's better to implement the page on

I can work on this.

Updated by stomar (Marcus Stollsteimer) over 8 years ago

I assume that 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 and then come back to 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 of course should be active as long as some officially supported branch points there.

Note also that 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 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

Updated by naruse (Yui NARUSE) over 4 years ago

  • Backport changed from 1.9.3: UNKNOWN, 2.0.0: UNKNOWN to 2.1: DONTNEED, 2.2: DONTNEED, 2.3: DONTNEED
  • Status changed from Feedback to Closed

Also available in: Atom PDF