From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ffbox0-bg.mplayerhq.hu (ffbox0-bg.ffmpeg.org [79.124.17.100]) by master.gitmailbox.com (Postfix) with ESMTP id 9E44244C32 for ; Mon, 14 Nov 2022 09:13:58 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id BD54168BD77; Mon, 14 Nov 2022 11:13:35 +0200 (EET) Received: from mail0.khirnov.net (red.khirnov.net [176.97.15.12]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id B599468BD5A for ; Mon, 14 Nov 2022 11:13:27 +0200 (EET) Received: from localhost (localhost [IPv6:::1]) by mail0.khirnov.net (Postfix) with ESMTP id 7693D2404F8 for ; Mon, 14 Nov 2022 10:13:27 +0100 (CET) Received: from mail0.khirnov.net ([IPv6:::1]) by localhost (mail0.khirnov.net [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id TlBtpW9caLNO for ; Mon, 14 Nov 2022 10:13:25 +0100 (CET) Received: from libav.khirnov.net (libav.khirnov.net [IPv6:2a00:c500:561:201::7]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "libav.khirnov.net", Issuer "smtp.khirnov.net SMTP CA" (verified OK)) by mail0.khirnov.net (Postfix) with ESMTPS id 17494240499 for ; Mon, 14 Nov 2022 10:13:25 +0100 (CET) Received: from libav.khirnov.net (libav.khirnov.net [IPv6:::1]) by libav.khirnov.net (Postfix) with ESMTP id 804443A054D for ; Mon, 14 Nov 2022 10:13:17 +0100 (CET) From: Anton Khirnov To: ffmpeg-devel@ffmpeg.org Date: Mon, 14 Nov 2022 10:13:09 +0100 Message-Id: <20221114091309.15755-4-anton@khirnov.net> X-Mailer: git-send-email 2.35.1 In-Reply-To: <20221114091309.15755-1-anton@khirnov.net> References: <20221114091309.15755-1-anton@khirnov.net> MIME-Version: 1.0 Subject: [FFmpeg-devel] [PATCH 4/4] doc/developer.texi: refine the "contributing code" section X-BeenThere: ffmpeg-devel@ffmpeg.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: FFmpeg development discussions and patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: FFmpeg development discussions and patches Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: Drop the reference to directly committing code, because - it is highly discouraged and very rarely done these days - there is no good reason NOT to submit patches for review Add a link to the development policy chapter. --- doc/developer.texi | 14 +++++--------- 1 file changed, 5 insertions(+), 9 deletions(-) diff --git a/doc/developer.texi b/doc/developer.texi index 2e050edc6a..cf918ac6b1 100644 --- a/doc/developer.texi +++ b/doc/developer.texi @@ -46,15 +46,10 @@ consult @url{https://ffmpeg.org/legal.html}. @section Contributing code -There are 2 ways by which code gets into FFmpeg: -@itemize @bullet -@item Submitting patches to the ffmpeg-devel mailing list. - See @ref{Submitting patches} for details. -@item Directly committing changes to the main tree. -@end itemize - -Whichever way, changes should be reviewed by the maintainer of the code -before they are committed. And they should follow the @ref{Coding Rules}. +All proposed code changes should be submitted for review to +@url{mailto:ffmpeg-devel@@ffmpeg.org, the development mailing list}, as +described in more detail in the @ref{Submitting patches} chapter. The code +should comply with the @ref{Development Policy} and follow the @ref{Coding Rules}. The developer making the commit and the author are responsible for their changes and should try to fix issues their commit causes. @@ -267,6 +262,7 @@ For Emacs, add these roughly equivalent lines to your @file{.emacs.d/init.el}: (setq c-default-style "ffmpeg") @end lisp +@anchor{Development Policy} @chapter Development Policy @section Patches/Committing -- 2.35.1 _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".