From 0de3c8283ec3a7201957fa20b8cf4de72cb69fb1 Mon Sep 17 00:00:00 2001
From: Hans Leidekker <hans@it.vu.nl>
Date: Mon, 27 Sep 2004 20:32:13 +0000
Subject: [PATCH] Suggest running conformance tests prior to sending a patch.

---
 documentation/patches.sgml | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/documentation/patches.sgml b/documentation/patches.sgml
index cfb8d6135eb..482adaf5beb 100644
--- a/documentation/patches.sgml
+++ b/documentation/patches.sgml
@@ -201,7 +201,13 @@ code
       <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>