contribute.html: compare pre/post patch testresults (was: [PATCH]: GCC Scheduler support for R10000 on MIPS)

[Ralf Wildenhues]

* Richard Sandiford wrote on Mon, Aug 04, 2008 at 09:05:36PM CEST:
> 
> In general, the thing to do is compare the post-patch results with the
> pre-patch results.

Well, if that is the thing to do _in general_, then it should be
openly stated as such.  OK for the web?

Thanks,
Ralf

2008-08-04  Ralf Wildenhues  <Ralf.Wildenhues@gmx.de>

	* htdocs/contribute.html (testing): Test results should be
	compared to pre-patch or gcc-testresults list data.

Index: htdocs/contribute.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/contribute.html,v
retrieving revision 1.69
diff -u -r1.69 contribute.html
--- htdocs/contribute.html	24 Feb 2008 14:03:12 -0000	1.69
+++ htdocs/contribute.html	4 Aug 2008 19:19:00 -0000
@@ -90,7 +90,10 @@
 feature.  If the test framework permits, you should automate these
 tests and add them to GCC's testsuite.  You must also perform
 regression tests to ensure that your patch does not break anything
-else.</p>
+else.  Typically, this means comparing post-patch test results to
+pre-patch results by testing twice or comparing with recent posts to
+the <a href="http://gcc.gnu.org/ml/gcc-testresults/">gcc-testresults
+list</a>.</p>
 
 <h3>Which tests to perform</h3>