[SCM] libav/experimental: Clarify bug reporting policy with regard to releases.

[siretart at users.alioth.debian.org]

The following commit has been merged in the experimental branch:
commit 2c880fe10137dbd18873cfb0f9b2a5a7c8eb3e41
Author: Diego Biurrun <diego at biurrun.de>
Date:   Mon Jul 19 08:41:47 2010 +0000

    Clarify bug reporting policy with regard to releases.
    
    Originally committed as revision 24322 to svn://svn.ffmpeg.org/ffmpeg/trunk

diff --git a/doc/faq.texi b/doc/faq.texi
index 6229666..7b0c75a 100644
--- a/doc/faq.texi
+++ b/doc/faq.texi
@@ -20,10 +20,11 @@ request more timely and/or frequent releases unless you are willing to
 help out creating them.
 
 @section I have a problem with an old version of FFmpeg; where should I report it?
-Nowhere. Upgrade to the latest release or if there is no recent release upgrade
-to Subversion HEAD. You could also try to report it. Maybe you will get lucky and
-become the first person in history to get an answer different from "upgrade
-to Subversion HEAD".
+Nowhere. We do not support old FFmpeg versions in any way, we simply lack
+the time, motivation and manpower to do so. If you have a problem with an
+old version of FFmpeg, upgrade to the latest Subversion snapshot. If you
+still experience the problem, then you can report it according to the
+guidelines in @url{http://ffmpeg.org/bugreports.html}.
 
 @section Why doesn't FFmpeg support feature [xyz]?
 

-- 
Libav/FFmpeg packaging