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 AA0204BDF1 for ; Thu, 24 Jul 2025 17:42:23 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.ffmpeg.org (Postfix) with ESMTP id B821E68D7F1; Thu, 24 Jul 2025 20:42:19 +0300 (EEST) Received: from btbn.de (btbn.de [144.76.60.213]) by ffbox0-bg.ffmpeg.org (Postfix) with ESMTPS id 15C9368B8C6 for ; Thu, 24 Jul 2025 20:42:13 +0300 (EEST) Received: from [authenticated] by btbn.de (Postfix) with ESMTPSA id 79F0F27FD3372 for ; Thu, 24 Jul 2025 19:42:10 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rothenpieler.org; s=mail; t=1753378930; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=9PyGoQ9JahkslG7+QtEb6DzCpKnQ+i8ymyfsF9gd4Ho=; b=B8+LUwfSCr/Xzyn82czuuyT7AOizRz6szR6Mg+mBwLEyDWIVhdbhJI9jP//1MORW+F1O35 mBO0LDNlHzrr3JwPVfa/7mLbuK5iQGbYRs4BmzbhHDB/MHXafjaxypZZHZH4FC2kgEH+ve VIrYN6CYVKWGNUq0tyWejB8PGeA7LvfTF8k6pS5qg4zfm77Ui6e1Dwk/g8u+YHfS/A5ZwX rXnmel3mCT+/kIhu5S31aHjhNvgGzLc3QbxVSUfi/AMk6Mb09+WEjtlNVI9irVsuRZIyJO YPaqxlTMlL4H1H+HVYkdXjhvVylJSsNk9qFnQBvj5nt4zFtmnaw5qoM7on8EqA== Message-ID: Date: Thu, 24 Jul 2025 19:42:11 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird To: ffmpeg-devel@ffmpeg.org References: <9fe76bed-32d9-432e-be0a-be00a2a513c7@lynne.ee> Content-Language: en-US From: Timo Rothenpieler In-Reply-To: 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-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 7/24/2025 6:48 PM, Nicolas George wrote: > 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. Why? And who are "we"? Having a working Web-browser is a reasonable requirement in 2025. One could even make the counter argument that only being able to see patches as mail is not enough, and actively deters contributors and potential future maintainers. >> 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. The way it looks to me, there is only you, not an "us" or "we". I have not seen anyone except for you oppose the use of more modern tools. The only discussion ever was about which ones exactly, and hosted where by whom. The general expectation even seems to be that the ML will eventually become obsolete, though I don't see that happen anytime soon. >>> # 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? When did I promise that? That was something that was discussed at some point I think, but I do not remember _anyone_ making such a promise. It does not seem like a realistic goal to me either. Translating mails to patches is not something that's easily done, as proven by patchwork. Once the spamminess problem has been figured out, notifications about PRs will be forwarded to the ML again. So that direction will work fine, just not as format-patch patches, but references to PRs. What I do remember is the requirement to be able to largely/completely interact with the tool via CLI. And you can interact with forgejo nearly entirely via cli with one of multiple tools made for it (and plain git itself of course). The most feature complete being https://gitea.com/gitea/tea There's multiple ones in active development, so you can pick your favourite. And you can reply to notification mails from it directly via mail, just not when the ML is forwarding them it seems. _______________________________________________ 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".