split patches up as far as sensibly possible, but no further.

git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@13415 b3059339-0415-0410-9bf9-f77b7e298cf2
This commit is contained in:
diego 2004-09-21 08:39:12 +00:00
parent 70d2a48322
commit f8562647cb
1 changed files with 5 additions and 3 deletions

View File

@ -46,9 +46,11 @@ that your patch will be included.
speak several languages you are of course welcome to update some of the
translations as well.
7. If you make independent changes, try to send them as separate patches.
If your patch is very big, try splitting it into several self-contained
pieces. Each part can then be reviewed and committed separately.
7. If you make independent changes, try to send them as separate patches
in separate mails. Likewise, if your patch is very big, try splitting
it into several self-contained pieces. Each part can then be reviewed
and committed separately. Logical units should stay together, though,
e.g. do not send a patch for every file you change.
8. Send your patch to the mplayer-dev-eng mailing list as a base64-encoded
attachment with the subject line: