aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMichael Niedermayer <michaelni@gmx.at>2003-12-27 15:21:17 +0000
committerMichael Niedermayer <michaelni@gmx.at>2003-12-27 15:21:17 +0000
commit54fcf429cd6031896410b3d632da98070388f595 (patch)
treece8c0989169813d4db7309f33528c4b0e10dec4f
parent1c004e5622378cd62f574083f5d7651c0e455036 (diff)
downloadffmpeg-54fcf429cd6031896410b3d632da98070388f595.tar.gz
its nice to include 'what it does & why' in submitted patches
Originally committed as revision 2631 to svn://svn.ffmpeg.org/ffmpeg/trunk
-rw-r--r--doc/ffmpeg-doc.texi4
1 files changed, 4 insertions, 0 deletions
diff --git a/doc/ffmpeg-doc.texi b/doc/ffmpeg-doc.texi
index da2266e5e8..abe66784fe 100644
--- a/doc/ffmpeg-doc.texi
+++ b/doc/ffmpeg-doc.texi
@@ -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