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 60AD54F078 for ; Fri, 16 May 2025 09:50:41 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.ffmpeg.org (Postfix) with ESMTP id 1C4D268CA0D; Fri, 16 May 2025 12:50:38 +0300 (EEST) Received: from nef.ens.fr (nef2.ens.fr [129.199.96.40]) by ffbox0-bg.ffmpeg.org (Postfix) with ESMTPS id EFC5E68CA06 for ; Fri, 16 May 2025 12:50:30 +0300 (EEST) X-ENS-nef-client: 129.199.129.80 ( name = phare.normalesup.org ) Received: from phare.normalesup.org (phare.normalesup.org [129.199.129.80]) by nef.ens.fr (8.14.4/1.01.28121999) with ESMTP id 54G9oUgf029956 for ; Fri, 16 May 2025 11:50:30 +0200 Received: by phare.normalesup.org (Postfix, from userid 1001) id 390E82EFD9; Fri, 16 May 2025 11:50:30 +0200 (CEST) Date: Fri, 16 May 2025 11:50:30 +0200 From: Nicolas George To: FFmpeg development discussions and patches Message-ID: References: <20250515211148.6C91C4128B8@natalya.videolan.org> <7080a655-035e-e56f-a97c-5579edb2e760@passwd.hu> <20250516005421.GX29660@pb2> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (nef.ens.fr [129.199.96.32]); Fri, 16 May 2025 11:50:30 +0200 (CEST) Subject: Re: [FFmpeg-devel] [FFmpeg-cvslog] fftools/graphprint: Now, make it a Killer-Feature! 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: softworkz . (HE12025-05-16): > Sadly, this is once another feature from which FFmpeg > developers are thinking that you should not have it. > > I have tried my best, but I have no interest in endless > arguing and upsetting everybody, so this feature dies > here officially. Or you could find alternate method of implementing it that do not have the flaws that your senior developers have pointed. Your choice: play the victim or accept counsel. -- Nicolas George _______________________________________________ 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".