commit 0de3c8283ec3a7201957fa20b8cf4de72cb69fb1
author Hans Leidekker <hans@it.vu.nl> Mon Sep 27 20:32:13 2004 +0000
committer Alexandre Julliard <julliard@winehq.org> Mon Sep 27 20:32:13 2004 +0000
tree 267d0a63220d2d34004421b9339029014c3d5086
parent 6e7d28d50295b8b30b2255c5b52dfd35a34ee294

Suggest running conformance tests prior to sending a patch.

documentation/patches.sgml

diff --git a/documentation/patches.sgml b/documentation/patches.sgml
index cfb8d61..482adaf 100644
--- a/documentation/patches.sgml
+++ b/documentation/patches.sgml
@@ -201,7 +201,13 @@
       <para>
         Save yourself some embarrassment and run your patched code
         against more than just your current test example.  Experience
-        will tell you how much effort to apply here.
+        will tell you how much effort to apply here. If there are
+        any conformance tests for the code you're working on, run them
+        and make sure they still pass after your patch is applied. Running
+        tests can be done by running <command>make test</command>. You may
+        need to run <command>make testclean</command> to undo the results
+        of a previous test run. See the <quote>testing</quote> guide for
+        more details on Wine's conformance tests.
       </para>
 
     </sect1>