# HG changeset patch
# User diego
# Date 1049386864 0
# Node ID 61ba1af7d87b5f56da2a4ea357cbe6a413b52c0a
# Parent  eb55fee443d26ea86eaa910f840928636250ab42
Explain the need for unified diffs.

diff -r eb55fee443d2 -r 61ba1af7d87b DOCS/tech/patches.txt
--- a/DOCS/tech/patches.txt	Thu Apr 03 16:11:37 2003 +0000
+++ b/DOCS/tech/patches.txt	Thu Apr 03 16:21:04 2003 +0000
@@ -10,7 +10,8 @@
    out CVS and daily CVS snapshots are available from our download page.
    We do not accept patches for releases or outdated CVS versions.
 
-2. Make unified diffs ('diff -Naur' or 'cvs diff -u').
+2. Make unified diffs ('diff -Naur' or 'cvs diff -u'). Unified diffs can easily
+   be applied with 'patch'. This is much harder with other diff types.
 
 3. Test the functionality of your patch. We'll *refuse* it if it breaks
    something, even if it extends other features!