diff options
author | diego <diego@b3059339-0415-0410-9bf9-f77b7e298cf2> | 2002-08-30 00:53:11 +0000 |
---|---|---|
committer | diego <diego@b3059339-0415-0410-9bf9-f77b7e298cf2> | 2002-08-30 00:53:11 +0000 |
commit | f89c93719c963f40531f7fac586e601c6f244b9c (patch) | |
tree | 0053e23243c3d7746f1b42717879c9e9f3d39d7c /DOCS/tech/patches.txt | |
parent | 9b016a46876a816805721025b4bb66d1640abf1f (diff) | |
download | mpv-f89c93719c963f40531f7fac586e601c6f244b9c.tar.bz2 mpv-f89c93719c963f40531f7fac586e601c6f244b9c.tar.xz |
Explain why putting [PATCH] in the subject is important.
git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@7154 b3059339-0415-0410-9bf9-f77b7e298cf2
Diffstat (limited to 'DOCS/tech/patches.txt')
-rw-r--r-- | DOCS/tech/patches.txt | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/DOCS/tech/patches.txt b/DOCS/tech/patches.txt index 5d7ceae391..dca43fb7aa 100644 --- a/DOCS/tech/patches.txt +++ b/DOCS/tech/patches.txt @@ -29,6 +29,9 @@ time for fixing buggy, broken or old patches! Subject line should be: '[PATCH] very short description of the patch'. In the mail, describe in a few sentences what you change and why. If you made independent changes, try to send them as separate patches. + The subject line is very important if you do not want your patch to get + lost in the noise. We need the uppercase [PATCH] to be able to search + for unapplied patches, so please use it. Thank you! |