Revision 71aed40b doc/developer.texi

View differences:

doc/developer.texi
321 321
@item
322 322
    Does fate pass with the patch applied? (make fate)
323 323
@item
324
    Is the patch a unified diff?
324
    Was the patch generated with git format-patch or send-email?
325 325
@item
326 326
    Is the patch against latest FFmpeg git master branch?
327 327
@item
......
342 342
    tools/trasher and the noise bitstream filter. Your decoder or demuxer
343 343
    should not crash or end in a (near) infinite loop when fed damaged data.
344 344
@item
345
    Is the patch created from the root of the source tree, so it can be
346
    applied with @code{patch -p0}?
347
@item
348 345
    Does the patch not mix functional and cosmetic changes?
349 346
@item
350 347
    Did you add tabs or trailing whitespace to the code? Both are forbidden.
......
379 376
@item
380 377
    Lines with similar content should be aligned vertically when doing so
381 378
    improves readability.
382
@item
383
    Did you provide a suggestion for a clear commit log message?
384 379
@end enumerate
385 380

  
386 381
@section Patch review process

Also available in: Unified diff