From 26c5dea7ba6c31dd7a46fa2f70f12faf27ef0add Mon Sep 17 00:00:00 2001 From: diego Date: Thu, 3 Apr 2003 16:21:04 +0000 Subject: Explain the need for unified diffs. git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@9817 b3059339-0415-0410-9bf9-f77b7e298cf2 --- DOCS/tech/patches.txt | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'DOCS/tech/patches.txt') diff --git a/DOCS/tech/patches.txt b/DOCS/tech/patches.txt index f3db528415..f30fbcd514 100644 --- a/DOCS/tech/patches.txt +++ b/DOCS/tech/patches.txt @@ -10,7 +10,8 @@ outdated patches. 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! -- cgit v1.2.3