From 63662eb46d1f58dfb0671cba79c5547774d04567 Mon Sep 17 00:00:00 2001 From: diego Date: Mon, 20 Oct 2003 13:46:49 +0000 Subject: Explain why sending complete files is a bad idea. git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@11192 b3059339-0415-0410-9bf9-f77b7e298cf2 --- DOCS/tech/patches.txt | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'DOCS/tech/patches.txt') diff --git a/DOCS/tech/patches.txt b/DOCS/tech/patches.txt index aeb5b09d72..72d2c7d315 100644 --- a/DOCS/tech/patches.txt +++ b/DOCS/tech/patches.txt @@ -6,6 +6,10 @@ maintaining a big and complex software project is even harder, so please accept our rules. We cannot afford to spend our time fixing buggy, broken or 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. + 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. We do not accept patches for releases or outdated CVS versions. -- cgit v1.2.3