1
0
mirror of https://github.com/FFmpeg/FFmpeg.git synced 2024-12-23 12:43:46 +02:00

its nice to include 'what it does & why' in submitted patches

Originally committed as revision 2631 to svn://svn.ffmpeg.org/ffmpeg/trunk
This commit is contained in:
Michael Niedermayer 2003-12-27 15:21:17 +00:00
parent 1c004e5622
commit 54fcf429cd

View File

@ -932,6 +932,10 @@ encoding which ensures that the patch wont be trashed during
transmission) to the ffmpeg-devel mailinglist, see transmission) to the ffmpeg-devel mailinglist, see
@url{http://lists.sourceforge.net/lists/listinfo/ffmpeg-devel} @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 @section Regression tests
Before submitting a patch (or committing with CVS), you should at least Before submitting a patch (or committing with CVS), you should at least