From 865c125dda396f42a4afd1303707d2a0af5d43b5 Mon Sep 17 00:00:00 2001 From: diego Date: Mon, 20 Oct 2003 22:51:20 +0000 Subject: [PATCH] More precise wording inspired by michaelni. git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@11197 b3059339-0415-0410-9bf9-f77b7e298cf2 --- DOCS/tech/patches.txt | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/DOCS/tech/patches.txt b/DOCS/tech/patches.txt index 72d2c7d315..d1a9e2c69e 100644 --- a/DOCS/tech/patches.txt +++ b/DOCS/tech/patches.txt @@ -8,7 +8,8 @@ outdated patches. 0. Do not send complete files. These need to be diffed by hand to see the changes, which makes reviews harder and less likely to occur. Besides as - soon as one of the files changes, your version becomes obsolete. + soon as one of the files changes, your version becomes harder to apply, + thus reducing its chances of being accepted. 1. Always make patches for the CVS version. The README describes how to check out CVS and daily CVS snapshots are available from our download page.