improved message

[craig@jcb-sc.com]

>The point with the last line was to suggest to the users that there
>will be some people reading the bug report, so they should do a good
>job when writing the report.

Okay, that seems reasonable.

>  >I'd suggest eliminating the last line, and appending "." to the
>  >preceding one, to terminate the message (apparently a newline
>  >is not appropriate there, as it wasn't present in the existing code).
>
>I include here two versions, one with and one without the last line,
>so you can pick which one you want to install (are you going to?).

I'd rather leave that to Jeff or someone else more aware of issues
like how it might affect the testsuite.  Either version is fine by
me, by the way.

>What about one other suggestion in my original message that the link
>in http://egcs.cygnus.com/faq.html#bugreport that points to the bug
>report section in the egcs manual could actualy point there the same way
> http://egcs.cygnus.com/onlinedocs/g77_bugs.html does. 
>Probably there is some wizardry involved in generating the html files
>from the texi documents so the name of the file containing the bugs
>sections stays the same. I presume you were involved in doing it for g77, could you do it in this case too? 

I didn't do the WWW setup for g77, I think Jeff did.  Yes, it'd be
nice if the same kind of "direct pointing" was done for gcc, et al.

One concern I have: maybe it'd reduce confusion if the bug-reporting
diagnostic, as well as the installation documentation, throughout egcs --
basically anything with a URL to the EGCS site -- include, in the URL,
the version number of EGCS (GCC) somehow.

That way, users are directed to the appropriate bug-submitting and/or
installation instructions *for the version of GCC they have*.

        tq vm, (burley)