summaryrefslogtreecommitdiff
path: root/doc/optimization.txt
diff options
context:
space:
mode:
authorJohan Andersson <j@i19.se>2011-03-13 23:29:19 +0100
committerRonald S. Bultje <rsbultje@gmail.com>2011-03-13 18:45:29 -0400
commit21de920472cc3d338312957bfd03dcac278b5ae3 (patch)
tree3f22e02f5e518a738ed8307dcdf02a9e44c36140 /doc/optimization.txt
parent0e6a3ee4fa317f674a3e895188620aa5839cc414 (diff)
Update the url to the site website and change ffmpeg-devel to libav-devel
Signed-off-by: Ronald S. Bultje <rsbultje@gmail.com>
Diffstat (limited to 'doc/optimization.txt')
-rw-r--r--doc/optimization.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/optimization.txt b/doc/optimization.txt
index 08954f9973..53cd21d22d 100644
--- a/doc/optimization.txt
+++ b/doc/optimization.txt
@@ -18,14 +18,14 @@ As many functions tend to be a bit difficult to understand because
of optimizations, it can be hard to optimize them further, or write
architecture-specific versions. It is recommended to look at older
revisions of the interesting files (web frontends for the various FFmpeg
-branches are listed at http://ffmpeg.org/download.html).
+branches are listed at http://libav.org/download.html).
Alternatively, look into the other architecture-specific versions in
the x86/, ppc/, alpha/ subdirectories. Even if you don't exactly
comprehend the instructions, it could help understanding the functions
and how they can be optimized.
NOTE: If you still don't understand some function, ask at our mailing list!!!
-(http://lists.mplayerhq.hu/mailman/listinfo/ffmpeg-devel)
+(https://lists.libav.org/mailman/listinfo/libav-devel)
When is an optimization justified?