virtualenv/FFmpeg
1
0
Fork 0
mirror of https://github.com/FFmpeg/FFmpeg.git synced 2025-04-14 00:58:38 +02:00
Code Issues Releases Activity

Attempt to better explain how to split patches into individual

Browse Source 
self-contained pieces.

Originally committed as revision 10108 to svn://svn.ffmpeg.org/ffmpeg/trunk
This commit is contained in:
Diego Biurrun 2007-08-13 22:15:48 +00:00
parent 9488b966c7
commit e1669c5ebe
1 changed files with 6 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
doc/ffmpeg-doc.texi
View File

@ -1673,9 +1673,12 @@ First, (@pxref{Coding Rules}) above if you did not yet.
When you submit your patch, try to send a unified diff (diff '-up' When you submit your patch, try to send a unified diff (diff '-up'
option). We cannot read other diffs :-) option). We cannot read other diffs :-)
Also please do not submit patches which contain several unrelated changes. Also please do not submit a patch which contains several unrelated changes.
Split them into individual self-contained patches; this makes reviewing Split it into separate, self-contained pieces. This does not mean splitting
them much easier. file by file. Instead, make the patch as small as possible while still
keeping it as a logical unit that contains an individual change, even
if it spans multiple files. This makes reviewing your patches much easier
for us and greatly increases your chances of getting your patch applied.
Run the regression tests before submitting a patch so that you can Run the regression tests before submitting a patch so that you can
verify that there are no big problems. verify that there are no big problems.