# HG changeset patch
# User michael
# Date 1173962704 0
# Node ID e27b971ccae56c543840e8fda744bb98cb1c74e0
# Parent  e03a45f3a360fb80ea93bccca0b71eef8c047f9b
update spliting rule to what i just added to ffmpeg
comments welcome

diff -r e03a45f3a360 -r e27b971ccae5 DOCS/tech/new_policy_proposal.txt
--- a/DOCS/tech/new_policy_proposal.txt	Thu Mar 15 12:42:59 2007 +0000
+++ b/DOCS/tech/new_policy_proposal.txt	Thu Mar 15 12:45:04 2007 +0000
@@ -105,13 +105,13 @@
 
 Splitting changes
    Do not commit unrelated changes together, split them into self-contained
-   pieces.
-   if you have any doubt discuss it on the developer mailing list before
-   committing, also when in doubt more splitting is better then less, changes
-   which are larger then 10kbyte generally should be split into several
-   incremental changes if possible even if you think they are all related
-   keeping changes well split makes reviewing and understanding them on 
-   svn log at the time of commit and later when debugging a bug much easier
+   pieces. Also dont forget that if part B depends on part A but A doesnt
+   depend on B, then A can and should be commited first and seperately from B.
+   Keeping changes well split into self contained parts makes reviewing and
+   understanding them on svn log at the time of commit and later when
+   debugging a bug much easier.
+   Also if you have doubt about spliting or not spliting, dont hesitate to
+   ask/disscuss it on the developer mailing list.
 
 4. Do not change behavior of the program (renaming options etc) or
    remove functionality from the code without approval in a discussion on