This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

PATCH: bugs.html (was): Unifying Bug Reporting Instructions


On Fri, 13 Oct 2000, Gerald Pfeifer wrote:
> Yes, in fact I have been planing to do so. Once Alexandre has committed
> the changes to bugs.html we discussed yesterday, I'm going to do so --
> unless you beat me to it (i.e., consider such a change pre-approved). :-)

As promised. Plus the first step in reducing redundancy (and reference 
loops):

  We prefer to receive bug reports via GNATS. Do not refer to the info
  manual any longer.

Gerald

Index: bugs.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/bugs.html,v
retrieving revision 1.20
diff -c -3 -p -r1.20 bugs.html
*** bugs.html	2000/10/13 18:11:33	1.20
--- bugs.html	2000/10/18 01:38:20
***************
*** 13,23 ****
  
  <h1><a name="report">Reporting Bugs</a></h1>
  
! <p>The <a href="onlinedocs/">gcc info manual</a>, section Bugs contains
! complete instructions on how to report bugs.
! The manual can also be read using `<i>M-x <tt>info</tt></i>' in Emacs, or if
! the GNU <tt>info</tt> program is installed on your system by `<tt>info --node
! "(gcc)Bugs"</tt>'.
  
  <p>Before you report a bug, please check the <a href="#known">list of
  well-known bugs</a> and, if possible, try a newer development snapshot
--- 13,20 ----
  
  <h1><a name="report">Reporting Bugs</a></h1>
  
! <p>Our preferred way of receiving bugs is via our <a href="gnats.html">GNATS
! bug reporting system</a>.</p>
  
  <p>Before you report a bug, please check the <a href="#known">list of
  well-known bugs</a> and, if possible, try a newer development snapshot


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]