Commit 3bb213d7 authored by diego's avatar diego

Attempt to better explain how to split patches into individual

self-contained pieces.


git-svn-id: file:///var/local/repositories/ffmpeg/trunk@10108 9553f0bf-9b14-0410-a0b8-cfaf0461ba5b
parent 25b2de1d
......@@ -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'
option). We cannot read other diffs :-)
Also please do not submit patches which contain several unrelated changes.
Split them into individual self-contained patches; this makes reviewing
them much easier.
Also please do not submit a patch which contains several unrelated changes.
Split it into separate, self-contained pieces. This does not mean splitting
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
verify that there are no big problems.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment