[FFmpeg-cvslog] [ffmpeg.org]: r307 - in trunk/src: bugreports contact index

superdump subversion
Mon Mar 2 02:31:28 CET 2009


Author: superdump
Date: Mon Mar  2 02:31:27 2009
New Revision: 307

Log:
Move some content from the contact page to more appropriate places and reword
some of it to improve the tone

Modified:
   trunk/src/bugreports
   trunk/src/contact
   trunk/src/index

Modified: trunk/src/bugreports
==============================================================================
--- trunk/src/bugreports	Thu Feb 26 02:49:33 2009	(r306)
+++ trunk/src/bugreports	Mon Mar  2 02:31:27 2009	(r307)
@@ -11,6 +11,15 @@
 promises.
 </p>
 
+<p><strong>Are you using the latest SVN version of FFmpeg?</strong></p>
+
+<p>
+FFmpeg is in a state of perpetual development and we do not currently have the
+person power to backport fixes to official releases. As such, if you wish to
+query or report a bug, you must try with the latest SVN revision of FFmpeg to
+confirm the issue still exists.
+</p>
+
 <p>
 If you find a problem with FFmpeg, you can submit a report to the
 FFmpeg bug tracker at

Modified: trunk/src/contact
==============================================================================
--- trunk/src/contact	Thu Feb 26 02:49:33 2009	(r306)
+++ trunk/src/contact	Mon Mar  2 02:31:27 2009	(r307)
@@ -1,53 +1,5 @@
 <h1>Contact Us</h1>
 
-<p>
-Need help with FFmpeg? First, these very important questions:
-</p>
-
-<p><strong>Are you using the latest SVN version of FFmpeg?</strong></p>
-
-<p>
-Seriously, FFmpeg is in a state of perpetual development and "official"
-releases are highly infrequent and largely a formality. The releases do
-not reflect the state of the FFmpeg's current technology. You should be using
-the latest SVN checkout or snapshot package.
-</p>
-
-<p><strong>Have you configured FFmpeg with <code>--enable-libfaac
---enable-libmp3lame</code>?</strong></p>
-
-<p>
-Most of the times you are missing an AAC or MP3 encoder.
-Make sure you compile FFmpeg with these flags before you ask for help.
-</p>
-
-<p>
-Now then, if you are still experiencing problems with the latest, up to date
-SVN copy, check out the
-<a href="bugreports.html">FFmpeg bug report page</a>. Providing the
-kind of information requested on that page helps the developers help you
-with the problem you are reporting. It saves time for everyone. Simply
-writing "It does not work!" is remarkably useless and inevitably leads to
-an exchange where the developers must ask you to visit the bug reporting
-page anyway.
-</p>
-
-<p>
-After you have a good bug report, submit it to our bug tracker.
-</p>
-
-<p>
-<b>Want to participate in the active development of FFmpeg?</b> Keep up
-with the latest developments by subscribing to both the
-<a href="https://lists.mplayerhq.hu/mailman/listinfo/ffmpeg-devel/">ffmpeg-devel</a> and
-<a href="https://lists.mplayerhq.hu/mailman/listinfo/ffmpeg-cvslog/">ffmpeg-cvslog</a> lists.
-If you send us a patch, please make it a unified diff (diff -u), everything
-else is unusable. For more detailed guidelines, have a look at the
-<a href="http://www.mplayerhq.hu/DOCS/tech/patches.txt">MPlayer patch guidelines</a>
-most of what is written there applies to FFmpeg as well.
-</p>
-
-
 <h2>Mailing lists</h2>
 
 <p>
@@ -60,8 +12,16 @@
 If you attach files, avoid compressing small files, uncompressed is preferred.
 Also please try to avoid posting mails with overly long signatures or nonsense
 corporate disclaimers that claim the content of your mails is confidential.
+</p>
+<p>
 Attached patches should not have application/octet-stream as mime-type, but
 text/plain or even better text/x-diff or text/x-patch.
+If you send us a patch, please make it some form of unified diff. We prefer
+patches made using <code>svn diff > submission.diff</code> from the root of
+your FFmpeg checkout, but we also accept git patches. For more detailed
+guidelines, have a look at the
+<a href="http://www.mplayerhq.hu/DOCS/tech/patches.txt">MPlayer patch guidelines</a>
+most of what is written there applies to FFmpeg as well.
 Trespass these rules at the risk of being flamed.
 </p>
 

Modified: trunk/src/index
==============================================================================
--- trunk/src/index	Thu Feb 26 02:49:33 2009	(r306)
+++ trunk/src/index	Mon Mar  2 02:31:27 2009	(r307)
@@ -20,6 +20,12 @@
 </p>
 
 <p>
+<b>Want to participate in the active development of FFmpeg?</b> Keep up
+with the latest developments by subscribing to both the
+<a href="contact.html">ffmpeg-devel and ffmpeg-cvslog</a> lists.
+</p>
+
+<p>
 <b>FFmpeg is free software and is licensed under the LGPL or GPL</b> depending
 on your choice of configuration options. If you use FFmpeg or its constituent
 libraries, you <b>must</b> adhere to the terms of the license in question.




More information about the ffmpeg-cvslog mailing list