[FFmpeg-devel] [PATCH] doc/developer: Add patchwork mentioning to "patch submission checklist"

Jonathan Campbell jonathan at impactstudiopro.com
Wed Sep 7 17:19:00 EEST 2016

On 09/07/2016 04:51 AM, Michael Niedermayer wrote:
> Signed-off-by: Michael Niedermayer <michael at niedermayer.cc>
> ---
>  doc/developer.texi | 6 ++++++
>  1 file changed, 6 insertions(+)
> diff --git a/doc/developer.texi b/doc/developer.texi
> index 4d3a7ae..51e3da7 100644
> --- a/doc/developer.texi
> +++ b/doc/developer.texi
> @@ -641,6 +641,12 @@ are notoriously left unchecked, which is a serious problem.
>  @item
>  Test your code with valgrind and or Address Sanitizer to ensure it's free
>  of leaks, out of array accesses, etc.
> +
> + at item
> +Check that your submitted patch shows up on @url{https://patchwork.ffmpeg.org}.
> +Also make sure its status is updated, you can create an account and update it.
> +If your patch is incorrectly or not listed in patchwork then it might be
> +missed by developers using patchwork to find patches needing review or pushing.
>  @end enumerate
>  @section Patch review process

I only see one of the 4 patches for AC-3 consistent noise generation (the libavutil version bump) on the patchwork site. Can I assume the other three will make their way into the patchwork list when the time is right, or did I submit the patch wrong?

Jonathan Campbell

More information about the ffmpeg-devel mailing list