Uploading bug reports

[Joe Buck]

> I've been roaming through the egcs-bugs archives.  Many of these reports
> are rubbish that start out with "egcs told me to mail this address with
> a full report, so here I am".
> 
> Unfortunately, many these include things like the single line that made
> egcs bomb, no host or target information, no compilation options, and so
> on.  Since the specific message that is emitted by the compiler doesn't
> tell them what constitutes a good bug report or how to find more info,
> most don't seem to bother.

How about changing the "internal compiler message" to include a URL
where people can read up on what we need before they send the report?