This is the mail archive of the gcc-patches@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]
Other format: [Raw text]

Re: PATCH: faq.html -- remove "How do I report a bug?"


On Fri, 9 May 2003, Joseph S. Myers wrote:
> You consider that the compiler versions that gave faq.html#bugreport as
> the URL for reporting bugs are now sufficiently rarely used (or that bug
> reports against them are sufficiently unlikely to be of value) (both
> probably true, but those compilers are why the link was in the FAQ)?

Yes, and yes.

On Fri, 9 May 2003, Hans-Peter Nilsson wrote:
> The <URL:http://gcc.gnu.org/faq.html#bugreport> URL (or perhaps
> it's <URL:http://www.gnu.org/gcc/faq.html#bugreport>) should be
> preserved.  It appears in ICE messages of past releases.  I

True, but only for releases older than GCC 2.95.3, and bugs there will
in nearly all cases not be relevant for current development any longer,
so I considered the patch safe.

However, as you were sufficiently concerned to respond to the patch, I
have now committed the patch below:

  Add an anchor for #bugreport and a comment explaining why.
  Make the "commercial" option the last one in "How do I get a bug fixed
  or a feature added?". Also avoid explicitly refer mentioning GNATS and
  avoid a duplicate link.

Gerald

Index: faq.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/faq.html,v
retrieving revision 1.191
diff -u -3 -p -r1.191 faq.html
--- faq.html	9 May 2003 14:29:12 -0000	1.191
+++ faq.html	12 May 2003 12:09:51 -0000
@@ -164,36 +164,37 @@ than we've had before.</p>
 </blockquote>

 <hr />
-<h2><a name="support">How do I get a bug fixed or a feature added?</a></h2>
+<!-- The "bugreport" anchor was used in ICE messages of GCC < 2.95.3. -->
+<h2><a name="support"><a name="bugreport">How do I get a bug fixed or
+    a feature added?</a></a></h2>

 <p>There are lots of ways to get something fixed.  The list below may be
 incomplete, but it covers many of the common cases.  These are listed
-roughly in order of increasing difficulty for the average GCC user,
+roughly in order of decreasing difficulty for the average GCC user,
 meaning someone who is not skilled in the internals of GCC, and where
 difficulty is measured in terms of the time required to fix the bug.
 No alternative is better than any other; each has its benefits and
 disadvantages.</p>

 <ul>
-<li>Hire someone to fix it for you.  There are various companies and
-    individuals providing support for GCC.  This alternative costs
-    money, but is relatively likely to get results.</li>
+<li>Fix it yourself.  This alternative will probably bring results,
+    if you work hard enough, but will probably take a lot of time,
+    and, depending on the quality of your work and the perceived
+    benefits of your changes, your code may or may not ever make it
+    into an official release of GCC.</li>

-<li><a href="bugs.html">Report the problem to the GCC GNATS bug tracking system</a>
+<li><a href="bugs.html">Report the problem to the GCC bug tracking system</a>
     and hope that someone will be kind
     enough to fix it for you.  While this is certainly possible, and
     often happens, there is no guarantee that it will.  You should
     not expect the same response from this method that you would see
     from a commercial support organization since the people who read
     GCC bug reports, if they choose to help you, will be volunteering their
-    time.  This alternative will work best if you follow the directions
-    on <a href="bugs.html">submitting bugreports</a>.</li>
+    time.</li>

-<li>Fix it yourself.  This alternative will probably bring results,
-    if you work hard enough, but will probably take a lot of time,
-    and, depending on the quality of your work and the perceived
-    benefits of your changes, your code may or may not ever make it
-    into an official release of GCC.</li>
+<li>Hire someone to fix it for you.  There are various companies and
+    individuals providing support for GCC.  This alternative costs
+    money, but is relatively likely to get results.</li>
 </ul>

 <hr />


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