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]

Re: unwind-dw2-fde.[ch]


On Thu, 6 Sep 2001, Matthew Hudson wrote:

> (as opposed to actually work). If someone can point me to a page that
> tells me what the protocol is for actually getting a problem fixed and
> not ignored I'd really like that. Sorry about the rant but sheesh

http://gcc.gnu.org/faq.html#support

Though this ought to be mentioning GNATS rather than gcc-bugs; OK to
commit the following patch?

Index: faq.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/faq.html,v
retrieving revision 1.168
diff -u -r1.168 faq.html
--- faq.html	2001/08/31 14:52:23	1.168
+++ faq.html	2001/09/07 05:51:57
@@ -197,12 +197,13 @@
     individuals providing support for GCC.  This alternative costs
     money, but is relatively likely to get results.</li>
 
-<li>Report the problem to gcc-bugs and hope that someone will be kind
+<li>Report the problem to the GCC GNATS bug tracking system
+    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 gcc-bugs that you would see
+    not expect the same response from this method that you would see
     from a commercial support organization since the people who read
-    gcc-bugs, if they choose to help you, will be volunteering their
+    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>
 

-- 
Joseph S. Myers
jsm28@cam.ac.uk


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