Re: Updating bug reporting request error messages and docs togcc.gnu.org

[Gerald Pfeifer <pfeifer at dbai dot tuwien dot ac dot at>]

On 17 Jul 1999, Alexandre Oliva wrote:
> But here's one you can approve.  :-) It adds a couple of paragraphs
> with some details I've had to repeat to many bug reporters along the
> last few months.

Yes, that sounds like a good idea. (And this I can and will approve. ;-) )

Some minor comments:

  +<p>Typically the CPP output will be large, so please compress (with
  +maximum compression, <code>--best</code> or <code>-9</code>) the
  +resulting file with one of the popular compression programs such as
  +<tt>bzip2</tt>, <tt>gzip</tt>, <tt>zip</tt>, <tt>pkzip</tt> or
  +<tt>compress</tt> (in decreasing order of preference)

I am afraid that specifying --best and -9 might confuse some users
(Which option for which compressor?). Perhaps simply asking for maximum
compression is sufficient?

  +<code>.s</code>), you don't usually have to include it in the bug

"usually don't" instead?

+bug report in order to tell who should take care of it.  A meaningful
+subject, indicating the language and platform in which the bug
+occurred, also helps.

I stumbled over "in which the bug occurred", but I am not a native speaker
either. ;-)

+<p>If you fail to supply information enough information for a bug
                          ^^^^^^^^^^^        ^^^^^^^^^^^

-<h2><a name="multiple">How to install both multiple versions of gcc</a></h2>
+<h2><a name="multiple">How to install multiple versions of gcc</a></h2>

Oops! Hopefully Jeff and myself have not introduced too many bugs of this
kind while preparing the pages for the release.


Please install your patch, modulo any changes you consider appropriate.

Thanks!
Gerald
-- 
Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/