Re: Target-specific bugs

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

These are two follow-up patches I just committed.

Update reference to gnatswrite.html (and have it point to
bugs/management.html instead).

 and

Remove those parts that now reside in bugs/management.html.
By Chester Hosey <chosey at tr0n dot com>.

Gerald

Index: cvswrite.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/cvswrite.html,v
retrieving revision 1.51
diff -u -3 -p -r1.51 cvswrite.html
--- cvswrite.html	7 Dec 2002 13:51:44 -0000	1.51
+++ cvswrite.html	26 Mar 2003 21:17:13 -0000
@@ -12,8 +12,8 @@
 <h1>Read-write CVS access</h1>

 <p>We have read/write access to the CVS repository available for all
-our significant developers. Maintainers are also encouraged to edit
-the <a href="gnatswrite.html">GNATS database</a>.</p>
+our significant developers. Maintainers are also encouraged to <a
+href="bugs/management.html">edit our bugs database</a>.</p>

 <hr />
 <h2>Contents</h2>

Index: bugs.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/bugs.html,v
retrieving revision 1.66
diff -u -3 -p -r1.66 bugs.html
--- bugs.html	26 Mar 2003 01:51:47 -0000	1.66
+++ bugs.html	26 Mar 2003 21:17:14 -0000
@@ -24,7 +24,6 @@
  <li><a href="#pch">Detailed bug reporting instructions when using a precompiled header</a></li>
  </ul>
 </li>
-<li><a href="#manage">Managing Bugs (GNATS and the test-suite)</a></li>
 <li><a href="#known">Frequently Reported Bugs in GCC</a>
  <ul>
  <li><a href="#general">General</a></li>
@@ -275,45 +274,6 @@ use it.</p>
 <p>Please <strong>don't</strong> send us the actual precompiled
 header.  It is likely to be very large and we can't use it to
 reproduce the problem.</p>
-
-<h1><a name="manage">Managing Bugs (GNATS and the test-suite)</a></h1>
-
-<p>This section contains information mostly intended for GCC
-contributors.</p>
-
-<p>If you find a bug, but you are not fixing it (yet):</p>
-<ol>
-<li>Create a (minimal) test-case.</li>
-<li>Add the test-case to our test-suite, marking it as XFAIL unless
-the bug is a regression.</li>
-<li>Add a bug report referencing the test-case to GNATS.</li>
-</ol>
-
-<p>If you want to provide additional information in the bug tracking
-system about a reported bug:</p>
-<ol>
-<li>If the bug is a segmentation fault in the compiler,
-<a href="bugs/segfault.html">provide information about its location</a>.
-</li>
-<li><a href="bugs/minimize.html">Minimize the test case</a>.</li>
-<li>Try the test case with earlier and later versions of GCC to
-determine which versions it affects and whether it is a regression.
-If it is a regression, <a href="bugs/reghunt.html">identify the
-patch</a> that introduced it.</li>
-</ol>
-
-<p>If you fix a bug for which there is already a GNATS entry:</p>
-<ol>
-<li>Remove the XFAIL on the test-case.</li>
-<li>Close the bug report in GNATS.</li>
-</ol>
-
-<p>If you find a bug, and you are fixing it right then:</p>
-<ol>
-<li>Create a (minimal) test-case.</li>
-<li>Add the test-case to our test-suite, marking it as PASS.</li>
-<li>Check in your fixes.</li>
-</ol>

 <hr />