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

Ronald S. Bultje rsbultje at gmail.com
Wed Sep 7 15:03:20 EEST 2016


On Wed, Sep 7, 2016 at 7:51 AM, Michael Niedermayer <michael at niedermayer.cc>

> 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

I don't think we should require developers to use (or check, or update, or
create-an-account-on) patchwork. Wasn't the whole point of patchwork that
you can use it if you care, and you can ignore it if you don't care?


More information about the ffmpeg-devel mailing list