[FFmpeg-devel] [PATCH] doc/developer: remove merge request method of contributing

Josh de Kock josh at itanimul.li
Fri Apr 6 14:22:22 EEST 2018


On 2018/04/05 19:17, Lou Logan wrote:
> This seems to confuse Github users into thinking that we may accept pull
> requests. We do not accept pull requests.
> 
> Sending patches to the ffmpeg-devel mailing list is our preferred method
> for users to contribute code.
> 
> Signed-off-by: Lou Logan <lou at lrcd.com>
> ---
>   doc/developer.texi | 6 ++----
>   1 file changed, 2 insertions(+), 4 deletions(-)
> 
> diff --git a/doc/developer.texi b/doc/developer.texi
> index 0fc9c3f21c..a0eeefe242 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
> - at item Submitting patches to the main developer mailing list.
> + at item Submitting patches to the ffmpeg-devel mailing list.
>         See @ref{Submitting patches} for details.
>   @item Directly committing changes to the main tree.
> - at 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
> 

Consider removing 'Directly committing changes to the main tree.' as 
well. I'm not sure how often this is done, but certainly new 
contributors shouldn't be doing this.

-- 
Josh


More information about the ffmpeg-devel mailing list