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 C90894BDDD for ; Thu, 24 Jul 2025 16:48:58 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.ffmpeg.org (Postfix) with ESMTP id 476B068D799; Thu, 24 Jul 2025 19:48:54 +0300 (EEST) Received: from nef.ens.fr (nef2.ens.fr [129.199.96.40]) by ffbox0-bg.ffmpeg.org (Postfix) with ESMTPS id 8389968D0AB for ; Thu, 24 Jul 2025 19:48:47 +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 56OGmkcY014812 for ; Thu, 24 Jul 2025 18:48:47 +0200 Received: by phare.normalesup.org (Postfix, from userid 1001) id C15A42EFE3; Thu, 24 Jul 2025 18:48:46 +0200 (CEST) Date: Thu, 24 Jul 2025 18:48:46 +0200 From: Nicolas George To: FFmpeg development discussions and patches Message-ID: References: <9fe76bed-32d9-432e-be0a-be00a2a513c7@lynne.ee> 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]); Thu, 24 Jul 2025 18:48:47 +0200 (CEST) Subject: Re: [FFmpeg-devel] Notifications for the new monolithic tool 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: Timo Rothenpieler (HE12025-07-24): > I don't see any need for this, no. If the patch does not reach our inbox, it will not be reviewed. > That's what it does, just not as format-patch, but simply as a link. A link is not enough. When we open our mail, we need to be able to see the proposed change without an extra step. > And the mailing list is "a monolithic thing" as well, so there's no point > throwing shade like that. The mailing-list is just a mailing list, it does not try to combine a dozen different tools into one. > Patchwork tries to do that and it only semi-works, so I'd rather not. Then stop trying to force us to use mediocre tools. > > # View it on FFmpeg Forgejo ( https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20031 ) or reply to this email directly. > > is not adequate. > Yes it is, the mailing list just eats the Reply-To address, breaking it. No it is not: it requires an extra step. > It's been mentioned multiple times on the list and on IRC by now, and it > should be obvious that you can't just give yourself push/merge access on > your own anyway. I do not care about push access for now, I care about notifications. As libabvfilter maintainer, if somebody proposes a patch on libavfilter, I need to see it. You promised it would be possible to continue working through mail without extra work: did you lie? -- 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".