Mercurial > mplayer.hg

comparison DOCS/tech/patches.txt @ 13414:ea01d0554a6e

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
split patches up as far as sensibly possible, but no further.
author diego
date Tue, 21 Sep 2004 08:39:12 +0000
parents 7903766338f7
children 57d00d7a9182
comparison
equal deleted inserted replaced
13413:725f3fe7a97c 13414:ea01d0554a6e
44 update the documentation. The documentation maintainers will assist you 44 update the documentation. The documentation maintainers will assist you
45 in doing this. Updating the English documentation is enough. If you 45 in doing this. Updating the English documentation is enough. If you
46 speak several languages you are of course welcome to update some of the 46 speak several languages you are of course welcome to update some of the
47 translations as well. 47 translations as well.
48 48
49 7. If you make independent changes, try to send them as separate patches. 49 7. If you make independent changes, try to send them as separate patches
50 If your patch is very big, try splitting it into several self-contained 50 in separate mails. Likewise, if your patch is very big, try splitting
51 pieces. Each part can then be reviewed and committed separately. 51 it into several self-contained pieces. Each part can then be reviewed
52 and committed separately. Logical units should stay together, though,
53 e.g. do not send a patch for every file you change.
52 54
53 8. Send your patch to the mplayer-dev-eng mailing list as a base64-encoded 55 8. Send your patch to the mplayer-dev-eng mailing list as a base64-encoded
54 attachment with the subject line: 56 attachment with the subject line:
55 '[PATCH] very short description of the patch'. 57 '[PATCH] very short description of the patch'.
56 In the mail, describe in a few sentences what you change and why. 58 In the mail, describe in a few sentences what you change and why.