dont mention base64 about sending attachments.

this may (and has) confused people, beside
that 99.9% of all MUA will do the right thing
here anyways.


git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@30986 b3059339-0415-0410-9bf9-f77b7e298cf2
This commit is contained in:
attila 2010-04-02 17:29:22 +00:00
parent 103ca0c902
commit 0a49e5e96c
1 changed files with 2 additions and 2 deletions

View File

@ -56,8 +56,8 @@ that your patch will be included.
and committed separately. Logical units should stay together, though, and committed separately. Logical units should stay together, though,
i.e. do not send a patch for every file or directory you change. i.e. do not send a patch for every file or directory you change.
9. Send your patch to the mplayer-dev-eng mailing list as a base64-encoded 9. Send your patch to the mplayer-dev-eng mailing list as attachment with
attachment with the subject line: the subject line:
'[PATCH] very short description of the patch'. '[PATCH] very short description of the patch'.
In the mail, describe in a few sentences what you change and why. In the mail, describe in a few sentences what you change and why.
The subject line is very important if you do not want your patch to get The subject line is very important if you do not want your patch to get