Lines Matching +full:- +full:- +full:gcov +full:- +full:options
1 \input texinfo @c -*- texinfo -*-
2 @documentencoding UTF-8
23 best way to proceed is to send your patches to the ffmpeg-devel
35 @item Submitting patches to the ffmpeg-devel mailing list.
68 The presentation is one inspired by 'indent -i4 -kr -nut'.
79 Avoid Qt-style and similar Doxygen syntax with @code{!} in it, i.e. replace
178 For file-scope variables and functions declared as @code{static}, no prefix
197 retro-compatibility reasons. These exceptions are declared in the
242 (c-add-style "ffmpeg"
244 (c-basic-offset . 4)
245 (indent-tabs-mode . nil)
246 (show-trailing-whitespace . t)
247 (c-offsets-alist
248 (statement-cont . (c-lineup-assignments +)))
251 (setq c-default-style "ffmpeg")
259 @uref{http://www.gnu.org/licenses/lgpl-2.1.html, LGPL 2.1},
261 a gift-style license, the
262 @uref{http://opensource.org/licenses/isc-license.txt, ISC} or
263 @uref{http://mit-license.org/, MIT} license.
264 @uref{http://www.gnu.org/licenses/gpl-2.0.html, GPL 2} including
273 is unfinished but disabled may be permitted under-circumstances, like
289 over-testing things. If your code has problems (portability, triggers
294 They should be split them into self-contained pieces. Also do not forget
297 split into self-contained parts makes reviewing and understanding them on
308 the way we do. Send your changes as patches to the ffmpeg-devel mailing
318 force a given indentation style - we do not.). If you really need to make
339 Make sure the author of the commit is set correctly. (see git commit --author)
341 answer to ffmpeg-devel (or wherever you got the patch from) saying that
350 Send a patch to ffmpeg-devel. If no one answers within a reasonable
351 time-frame (12h for build failures and security fixes, 3 days small changes,
357 Do not change behavior of the programs (renaming options etc) or public
358 API or ABI without first discussing it on the ffmpeg-devel mailing list.
387 @subheading Subscribe to the ffmpeg-devel mailing list.
389 @uref{https://lists.ffmpeg.org/mailman/listinfo/ffmpeg-devel, ffmpeg-devel}
390 mailing list. Almost any non-trivial patch is to be sent there for review.
397 hold which messages from non-subscribers experience.
400 that you be subscribed to the ffmpeg-devel list. If you have a patch, and don't
404 @subheading Subscribe to the ffmpeg-cvslog mailing list.
406 @uref{https://lists.ffmpeg.org/mailman/listinfo/ffmpeg-cvslog, ffmpeg-cvslog}
412 unsure how best to do this, send a patch to ffmpeg-devel, the documentation
463 When you submit your patch, please use @code{git format-patch} or
464 @code{git send-email}. We cannot read other diffs :-).
467 Split it into separate, self-contained pieces. This does not mean splitting
487 @uref{https://lists.ffmpeg.org/mailman/listinfo/ffmpeg-devel, ffmpeg-devel}
488 mailing list. Use @code{git send-email} when possible since it will properly
490 as base64-encoded attachments, so your patch is not trashed during
492 (text/x-diff or text/x-patch or at least text/plain) and that only one
498 Using @code{git send-email} might not be desirable for everyone. The
500 way. It has been tested with Outlook and Thunderbird (with X-Unsent
506 git format-patch -s -o "outputfolder" --add-header "X-Unsent: 1" --suffix .eml --to ffmpeg-devel@ff…
570 @code{configure --disable-everything --enable-decoder=foo}
571 (or @code{--enable-demuxer} or whatever your component is)?
582 Was the patch generated with git format-patch or send-email?
585 Did you sign-off your patch? (@code{git commit -s})
586 …m/linux/kernel/git/torvalds/linux.git/plain/Documentation/process/submitting-patches.rst, Sign you…
587 of @dfn{sign-off}.
596 Are you subscribed to ffmpeg-devel?
634 Is the mime type of the patch correct? It should be text/x-diff or
635 text/x-patch or at least text/plain and not application/octet-stream.
676 If you added YASM code please check that things still work with --disable-yasm.
690 All patches posted to ffmpeg-devel will be reviewed, unless they contain a
730 @section Adding files to the fate-suite dataset
733 specific test then the media has to be included in the fate-suite.
739 the ffmpeg-devel mailing list, a direct link to download the sample media.
744 manner with the coverage tools @code{gcov}/@code{lcov}. This involves
750 @code{configure --toolchain=gcov}.
755 front-end tool provided by FFmpeg, in any combination.
764 You can use the command @code{make lcov-reset} to reset the coverage
772 @code{--toolchain=valgrind-memcheck} or @code{--toolchain=valgrind-massif}
778 @code{--target-exec='valgrind <your_custom_valgrind_options>} option in
811 on the @strong{ffmpeg-devel} mailing list in time to allow forward planning.
872 Propose and send a patch to the @strong{ffmpeg-devel} mailing list