its nice to include 'what it does & why' in submitted patches
authorMichael Niedermayer <michaelni@gmx.at>
Sat, 27 Dec 2003 15:21:17 +0000 (15:21 +0000)
committerMichael Niedermayer <michaelni@gmx.at>
Sat, 27 Dec 2003 15:21:17 +0000 (15:21 +0000)
Originally committed as revision 2631 to svn://svn.ffmpeg.org/ffmpeg/trunk

doc/ffmpeg-doc.texi

index da2266e5e8d115795c1a1753b9e4f3f4de3f7b69..abe66784fe1f0eaa8b077aeb45257f2bda3f82d1 100644 (file)
@@ -932,6 +932,10 @@ encoding which ensures that the patch wont be trashed during
 transmission) to the ffmpeg-devel mailinglist, see 
 @url{http://lists.sourceforge.net/lists/listinfo/ffmpeg-devel}
 
+It also helps quite a bit if you tell us what the patch does (for example
+'replaces lrint by lrintf') , and why (for example '*bsd isnt c99 compliant
+and has no lrint()')
+
 @section Regression tests
 
 Before submitting a patch (or committing with CVS), you should at least