comparison DOCS/tech/patches.txt @ 18361:e20114911d05

10l creating patches from root dir is already mentioned in item 2. roll back previous commit and make the text from item 2 a seperate item
author attila
date Sun, 30 Apr 2006 20:36:13 +0000
parents d604c7f2baba
children 71748783e001
comparison
equal deleted inserted replaced
18360:d604c7f2baba 18361:e20114911d05
16 out CVS and daily CVS snapshots are available from our download page. 16 out CVS and daily CVS snapshots are available from our download page.
17 We do not accept patches for releases or outdated CVS versions. 17 We do not accept patches for releases or outdated CVS versions.
18 18
19 2. Make unified diffs ('diff -Naur' or 'cvs diff -u'). Unified diffs can be 19 2. Make unified diffs ('diff -Naur' or 'cvs diff -u'). Unified diffs can be
20 applied easily with 'patch'. This is much harder with other diff types. 20 applied easily with 'patch'. This is much harder with other diff types.
21 Create the diff from the root of the MPlayer source tree, this makes the 21
22 3. Create the diff from the root of the MPlayer source tree, this makes the
22 diff easier to apply as it saves the step of changing to the correct 23 diff easier to apply as it saves the step of changing to the correct
23 directory. 24 directory.
24
25 3. Patches shoud always be created from the project root directory.
26 This simplifies applying a patch without first searching for the
27 right directory.
28 25
29 4. Test the functionality of your patch. We'll *refuse* it if it breaks 26 4. Test the functionality of your patch. We'll *refuse* it if it breaks
30 something, even if it extends other features! 27 something, even if it extends other features!
31 28
32 5. Read your patch. We'll *refuse* it if it changes indentation of the 29 5. Read your patch. We'll *refuse* it if it changes indentation of the