From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ffbox0-bg.ffmpeg.org (ffbox0-bg.ffmpeg.org [79.124.17.100]) by master.gitmailbox.com (Postfix) with ESMTPS id 858494C940 for ; Thu, 26 Jun 2025 06:51:35 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.ffmpeg.org (Postfix) with ESMTP id B5AA568E127; Thu, 26 Jun 2025 09:51:31 +0300 (EEST) Received: from mout-p-101.mailbox.org (mout-p-101.mailbox.org [80.241.56.151]) by ffbox0-bg.ffmpeg.org (Postfix) with ESMTPS id E628F68E126 for ; Thu, 26 Jun 2025 09:51:24 +0300 (EEST) Received: from smtp2.mailbox.org (smtp2.mailbox.org [IPv6:2001:67c:2050:b231:465::2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mout-p-101.mailbox.org (Postfix) with ESMTPS id 4bSTqZ1m26z9tCG for ; Thu, 26 Jun 2025 08:51:22 +0200 (CEST) Message-ID: <90f3ffe9-bc4e-4ce7-951e-d6dceb1ecc38@gyani.pro> Date: Thu, 26 Jun 2025 12:21:19 +0530 MIME-Version: 1.0 To: ffmpeg-devel@ffmpeg.org References: Content-Language: en-US From: Gyan Doshi In-Reply-To: X-Rspamd-Queue-Id: 4bSTqZ1m26z9tCG Subject: Re: [FFmpeg-devel] [PATCH] doc/developer: Fix typos 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-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: On 2025-06-26 12:16 pm, softworkz wrote: > From: softworkz > > Signed-off-by: softworkz > --- > doc/developer: Fix typos > > Published-As: https://github.com/ffstaging/FFmpeg/releases/tag/pr-ffstaging-103%2Fsoftworkz%2Fsubmit_typos-v1 > Fetch-It-Via: git fetch https://github.com/ffstaging/FFmpeg pr-ffstaging-103/softworkz/submit_typos-v1 > Pull-Request: https://github.com/ffstaging/FFmpeg/pull/103 > > doc/developer.texi | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/doc/developer.texi b/doc/developer.texi > index 108558b9e0..f4ae300c2b 100644 > --- a/doc/developer.texi > +++ b/doc/developer.texi > @@ -424,7 +424,7 @@ paste it from a random place, use an existing file as template. > @subheading You must not commit code which breaks FFmpeg! > This means unfinished code which is enabled and breaks compilation, > or compiles but does not work/breaks the regression tests. Code which > -is unfinished but disabled may be permitted under-circumstances, like > +is unfinished but disabled may be permitted under circumstances, like > missing samples or an implementation with a small subset of features. > Always check the mailing list for any reviewers with issues and test > FATE before you push. > @@ -546,7 +546,7 @@ FFmpeg also has a defined scope - your new API must fit within it. > > @subsubheading Replacing existing APIs > If your new API is replacing an existing one, it should be strictly superior to > -it, so that the advantages of using the new API outweight the cost to the > +it, so that the advantages of using the new API outweigh the cost to the > callers of changing their code. After adding the new API you should then > deprecate the old one and schedule it for removal, as described in > @ref{Removing interfaces}. LGTM. Regards, Gyan _______________________________________________ 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".