[SCM] libav/experimental: clarify previous revision on optimization justification

[siretart at users.alioth.debian.org]

The following commit has been merged in the experimental branch:
commit 07bf0cc9cf386a622fa27c9dc82fbeb11dff7c08
Author: Mike Melanson <mike at multimedia.cx>
Date:   Tue Jan 22 21:57:19 2008 +0000

    clarify previous revision on optimization justification
    
    Originally committed as revision 11598 to svn://svn.ffmpeg.org/ffmpeg/trunk

diff --git a/doc/optimization.txt b/doc/optimization.txt
index f5a86a3..27fcbba 100644
--- a/doc/optimization.txt
+++ b/doc/optimization.txt
@@ -30,15 +30,15 @@ NOTE: If you still don't understand some function, ask at our mailing list!!!
 
 When is an optimization justified?
 ----------------------------------
-Normally, clean & simple optimizations on widely used codecs can achieve
-an overall speedup of 0.1%. These speedups accumulate and can make a big
-difference after awhile. Also, if none of the following factors get
-worse due to an optimization -- speed, binary code size, source size,
-source readability -- and at least one factor improves, then an
-optimization is always a good idea even if the overall gain is less than
-0.1%. For obscure codecs that are not often used, the goal is more
-toward keeping the code clean, small, and readable than to make it 1%
-faster.
+Normally, clean and simple optimizations for widely used codecs are
+justified even if they only achieve an overall speedup of 0.1%. These
+speedups accumulate and can make a big difference after awhile. Also, if
+none of the following factors get worse due to an optimization -- speed,
+binary code size, source size, source readability -- and at least one
+factor improves, then an optimization is always a good idea even if the
+overall gain is less than 0.1%. For obscure codecs that are not often
+used, the goal is more toward keeping the code clean, small, and
+readable instead of making it 1% faster.
 
 
 WTF is that function good for ....:

-- 
Libav/FFmpeg packaging