summaryrefslogtreecommitdiffstats
path: root/DOCS
diff options
context:
space:
mode:
authordiego <diego@b3059339-0415-0410-9bf9-f77b7e298cf2>2006-12-04 10:24:00 +0000
committerdiego <diego@b3059339-0415-0410-9bf9-f77b7e298cf2>2006-12-04 10:24:00 +0000
commit11e03076eb022cfa4e3be9309c3f42d9488ba58a (patch)
tree9fd90f8de49432f650cfe44286ac04bcb1b23779 /DOCS
parent83cffbece8a609f5e5944cb9f83ad87257be818d (diff)
downloadmpv-11e03076eb022cfa4e3be9309c3f42d9488ba58a.tar.bz2
mpv-11e03076eb022cfa4e3be9309c3f42d9488ba58a.tar.xz
slight clarification
git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@21488 b3059339-0415-0410-9bf9-f77b7e298cf2
Diffstat (limited to 'DOCS')
-rw-r--r--DOCS/tech/patches.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/DOCS/tech/patches.txt b/DOCS/tech/patches.txt
index 1e818d8aa7..0df3514d2c 100644
--- a/DOCS/tech/patches.txt
+++ b/DOCS/tech/patches.txt
@@ -52,7 +52,7 @@ that your patch will be included.
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.
+ 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: