# HG changeset patch
# User diego
# Date 1165227840 0
# Node ID b52664db931c1aa2e87d1a13d49a39c7f4806dc8
# Parent  a9d9168516d928aa71738bb9a84eff7752c10cc1
slight clarification

diff -r a9d9168516d9 -r b52664db931c DOCS/tech/patches.txt
--- a/DOCS/tech/patches.txt	Mon Dec 04 09:30:15 2006 +0000
+++ b/DOCS/tech/patches.txt	Mon Dec 04 10:24:00 2006 +0000
@@ -52,7 +52,7 @@
     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: