X-Git-Url: https://git.sesse.net/?a=blobdiff_plain;f=doc%2Fdeveloper.texi;h=5c342c91064b8bdff5afe9c6bc6013bfb92b140c;hb=493240a522fca34882601fbeeda4e17aa40a0303;hp=66b24633063f7cfdecc1c9395e9670304d93bcde;hpb=9a15af48284b951701b7e6b9dcc81b4212c6ca95;p=ffmpeg diff --git a/doc/developer.texi b/doc/developer.texi index 66b24633063..5c342c91064 100644 --- a/doc/developer.texi +++ b/doc/developer.texi @@ -30,13 +30,11 @@ consult @url{https://ffmpeg.org/legal.html}. @chapter Contributing -There are 3 ways by which code gets into FFmpeg. +There are 2 ways by which code gets into FFmpeg: @itemize @bullet -@item Submitting patches to the main developer mailing list. +@item Submitting patches to the ffmpeg-devel mailing list. See @ref{Submitting patches} for details. @item Directly committing changes to the main tree. -@item Committing changes to a git clone, for example on github.com or - gitorious.org. And asking us to merge these changes. @end itemize Whichever way, changes should be reviewed by the maintainer of the code @@ -130,6 +128,9 @@ designated struct initializers (@samp{struct s x = @{ .i = 17 @};}); @item compound literals (@samp{x = (struct s) @{ 17, 23 @};}). +@item +for loops with variable definition (@samp{for (int i = 0; i < 8; i++)}); + @item Implementation defined behavior for signed integers is assumed to match the expected behavior for two's complement. Non representable values in integer @@ -562,9 +563,9 @@ Does @code{make fate} pass with the patch applied? Was the patch generated with git format-patch or send-email? @item -Did you sign off your patch? (git commit -s) -See @url{http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=blob_plain;f=Documentation/SubmittingPatches} for the meaning -of sign off. +Did you sign-off your patch? (@code{git commit -s}) +See @uref{https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/plain/Documentation/process/submitting-patches.rst, Sign your work} for the meaning +of @dfn{sign-off}. @item Did you provide a clear git commit log message?