summaryrefslogtreecommitdiffstats
path: root/DOCS
diff options
context:
space:
mode:
authorattila <attila@b3059339-0415-0410-9bf9-f77b7e298cf2>2010-04-02 17:29:22 +0000
committerattila <attila@b3059339-0415-0410-9bf9-f77b7e298cf2>2010-04-02 17:29:22 +0000
commit0a49e5e96c87375322be56417109ff12632a0323 (patch)
tree860475eab70f2a705fa8680bd241fb984a2dd349 /DOCS
parent103ca0c90258999d1f5dbb74c11ac837613a74ba (diff)
downloadmpv-0a49e5e96c87375322be56417109ff12632a0323.tar.bz2
mpv-0a49e5e96c87375322be56417109ff12632a0323.tar.xz
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
Diffstat (limited to 'DOCS')
-rw-r--r--DOCS/tech/patches.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/DOCS/tech/patches.txt b/DOCS/tech/patches.txt
index 692666d1a8..dfff16bf85 100644
--- a/DOCS/tech/patches.txt
+++ b/DOCS/tech/patches.txt
@@ -56,8 +56,8 @@ that your patch will be included.
and committed separately. Logical units should stay together, though,
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
- attachment with the subject line:
+ 9. Send your patch to the mplayer-dev-eng mailing list as attachment with
+ the subject line:
'[PATCH] very short description of the patch'.
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