[docs] winedev: A hint for patch separation (try 2)

André Hentschel nerv at dawncrow.de
Mon Jul 4 15:09:11 CDT 2011

As suggested by Jerome Leclanche

 en/winedev-coding.sgml |    4 ++++
 1 files changed, 4 insertions(+), 0 deletions(-)

diff --git a/en/winedev-coding.sgml b/en/winedev-coding.sgml
index eacf6d8..2788378 100644
--- a/en/winedev-coding.sgml
+++ b/en/winedev-coding.sgml
@@ -207,6 +207,10 @@ code
         is your friend!
+        Patches must not break building Wine nor its testsuite.
+        Adding dead code should also be avoided.
+      </para>
+      <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. If there are

Best Regards, André Hentschel

More information about the wine-patches mailing list