mirror of
https://gitee.com/openharmony/third_party_ffmpeg
synced 2024-11-28 21:50:37 +00: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:
parent
1c004e5622
commit
54fcf429cd
@ -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
|
||||
|
Loading…
Reference in New Issue
Block a user