Further bug reporting instructions

[Alexandre Oliva <oliva at lsd dot ic dot unicamp dot br>]

I decided to make it clearer that we need the preprocessed sources
even if the package is freely available elsewhere.  While I was at it,
I thought I'd also write that I prefer bug reports that are not in
archives, does anybody disagree with that?  Martin? :-)

Ok to install?

Index: bugs.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/bugs.html,v
retrieving revision 1.14
diff -u -c -r1.14 bugs.html
*** bugs.html	2000/03/04 14:00:03	1.14
--- bugs.html	2000/03/16 21:29:27
***************
*** 35,41 ****
    <li>The GCC version</li>
    <li>The system type</li>
    <li>All options you passed to the compiler</li>
!   <li>Preprocessed output of the source file that caused the compiler error</li>
  </ul>
  
  <p>All this can normally be accomplished by mailing the command line, the
--- 35,42 ----
    <li>The GCC version</li>
    <li>The system type</li>
    <li>All options you passed to the compiler</li>
!   <li>Preprocessed output of the source file that caused the compiler
!       error, even if the source code can be downloaded from elsewhere</li>
  </ul>
  
  <p>All this can normally be accomplished by mailing the command line, the
***************
*** 47,56 ****
  <p>Typically the CPP output (extension <code>.i</code> for C or
  <code>.ii</code> for C++) will be large, so please compress 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).  Use maximum
! compression (<code>-9</code>) if available.  Please include the
! compressed CPP output in your bug report.</p>
  
  <p>Since we're supposed to be able to re-create the assembly output
  (extension <code>.s</code>), you usually don't have to include it in
--- 48,58 ----
  <p>Typically the CPP output (extension <code>.i</code> for C or
  <code>.ii</code> for C++) will be large, so please compress the
  resulting file with one of the popular compression programs such as
! <tt>bzip2</tt>, <tt>gzip</tt>, <tt>zip</tt> or <tt>compress</tt> (in
! decreasing order of preference).  Use maximum compression
! (<code>-9</code>) if available.  Please include the compressed CPP
! output in your bug report, even if the source code is freely available
! elsewhere; it makes the job of our volunteer testers much easier.</p>
  
  <p>Since we're supposed to be able to re-create the assembly output
  (extension <code>.s</code>), you usually don't have to include it in
***************
*** 62,67 ****
--- 64,78 ----
  error output are in plain text, so that we don't have to decode the
  bug report in order to tell who should take care of it.  A meaningful
  subject indicating language and platform also helps.</p>
+ 
+ <p>Please avoid posting an archive (.tar, .shar or .zip); we generally
+ need just a single file to reproduce the bug (the .i/.ii preprocessed
+ file), and, by storing it in an archive, you're just making our
+ volunteers' jobs harder.  Only when your bug report requires multiple
+ source files to be reproduced should you use an archive.  But, even if
+ you feel you must use one, make sure the compiler version, output,
+ etc, are included in the bug report as plain text, not as part of the
+ archive.</p>
  
  <p>The gcc lists have message size limits (100 kbytes) and bug reports
  over those limits will currently be bounced.  We're trying to find a

-- 
Alexandre Oliva    Enjoy Guaranį, see http://www.ic.unicamp.br/~oliva/
Cygnus Solutions, a Red Hat company        aoliva@{redhat, cygnus}.com
Free Software Developer and Evangelist    CS PhD student at IC-Unicamp
oliva@{lsd.ic.unicamp.br, gnu.org}   Write to mailing lists, not to me