comparison DOCS/tech/patches.txt @ 11191:ed5969812ff3

Explain why sending complete files is a bad idea.
author diego
date Mon, 20 Oct 2003 13:46:49 +0000
parents 3a76cfb44e12
children 0750ab856742
comparison
equal deleted inserted replaced
11190:dad43bc55cfc 11191:ed5969812ff3
3 3
4 Note: We know our rules place a burden on you, but rest assured that 4 Note: We know our rules place a burden on you, but rest assured that
5 maintaining a big and complex software project is even harder, so please 5 maintaining a big and complex software project is even harder, so please
6 accept our rules. We cannot afford to spend our time fixing buggy, broken or 6 accept our rules. We cannot afford to spend our time fixing buggy, broken or
7 outdated patches. 7 outdated patches.
8
9 0. Do not send complete files. These need to be diffed by hand to see the
10 changes, which makes reviews harder and less likely to occur. Besides as
11 soon as one of the files changes, your version becomes obsolete.
8 12
9 1. Always make patches for the CVS version. The README describes how to check 13 1. Always make patches for the CVS version. The README describes how to check
10 out CVS and daily CVS snapshots are available from our download page. 14 out CVS and daily CVS snapshots are available from our download page.
11 We do not accept patches for releases or outdated CVS versions. 15 We do not accept patches for releases or outdated CVS versions.
12 16