While looking at this page before asking Jan-Benedict to add his tester, I noticed some updates to make here.
Streamline the first paragraph and split it in two. Remove reference to Michael Chastain's testing (which is not happening any more). Applied. Gerald Index: testing/index.html =================================================================== RCS file: /cvs/gcc/wwwdocs/htdocs/testing/index.html,v retrieving revision 1.28 diff -u -3 -p -r1.28 index.html --- testing/index.html 21 Oct 2012 12:16:40 -0000 1.28 +++ testing/index.html 18 Aug 2013 10:51:08 -0000 @@ -9,8 +9,9 @@ <h1>GCC Testing Efforts</h1> <p>This page describes regular efforts to test GCC thoroughly, plus ideas -for additional testing by volunteers who have machine cycles to spare. -For basic information about running the GCC testsuites, see +for additional testing.</p> + +<p>For information about running the GCC testsuites, see <a href="http://gcc.gnu.org/install/test.html";>Installing GCC: Testing</a>. For information about testsuite organization and adding new tests, see <a href="http://gcc.gnu.org/onlinedocs/gccint/Testsuites.html";> @@ -33,13 +34,6 @@ the test suite directories.</p> send their test results to the <a href="http://gcc.gnu.org/ml/gcc-testresults/";>gcc-testresults mailing list</a>.</li> - - <li>Michael Chastain runs the GDB test suite regularly and looks for - regressions caused by GCC debug output changes. He tests native - i686-pc-linux-gnu once every 4-10 days, and reports to the <a - href="http://gcc.gnu.org/ml/gcc-testresults/";>gcc-testresults</a> - and <a href="http://sourceware.org/ml/gdb-testers/";>gdb-testers</a> - mailing lists.</li> </ul> <h2>Ideas for further testing</h2>
