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 4E71D40ECB for ; Mon, 11 Apr 2022 08:29:06 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 4A7B868B367; Mon, 11 Apr 2022 11:29:04 +0300 (EEST) Received: from mail0.khirnov.net (red.khirnov.net [176.97.15.12]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 13CA768B292 for ; Mon, 11 Apr 2022 11:28:58 +0300 (EEST) Received: from localhost (localhost [IPv6:::1]) by mail0.khirnov.net (Postfix) with ESMTP id 8BF98240179 for ; Mon, 11 Apr 2022 10:28:57 +0200 (CEST) Received: from mail0.khirnov.net ([IPv6:::1]) by localhost (mail0.khirnov.net [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id duf_J5EhnNPq for ; Mon, 11 Apr 2022 10:28:56 +0200 (CEST) Received: from lain.red.khirnov.net (lain.red.khirnov.net [IPv6:2001:67c:1138:4306::3]) (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 "lain.red.khirnov.net", Issuer "smtp.khirnov.net SMTP CA" (verified OK)) by mail0.khirnov.net (Postfix) with ESMTPS id 38F022400F5 for ; Mon, 11 Apr 2022 10:28:56 +0200 (CEST) Received: by lain.red.khirnov.net (Postfix, from userid 1000) id 432761601AD; Mon, 11 Apr 2022 10:28:56 +0200 (CEST) From: Anton Khirnov To: FFmpeg development discussions and patches In-Reply-To: =?utf-8?q?=3CBN0P223MB0358DD034C459B1AD9DAB719BAE99=40BN0P223MB?= =?utf-8?q?0358=2ENAMP223=2EPROD=2EOUTLOOK=2ECOM=3E?= References: <20220404113037.13070-1-anton@khirnov.net> <20220405191542.GV2829255@pb2> <164918796468.24258.6158464741625303482@lain.red.khirnov.net> =?utf-8?q?=3C?= =?utf-8?q?DM8P223MB036517C3185EE467B97EF6B6BAE49=40DM8P223MB0365=2ENAMP223?= =?utf-8?q?=2EPROD=2EOUTLOOK=2ECOM=3E?= <164923451378.24258.12863595879743109558@lain.red.khirnov.net> =?utf-8?q??= =?utf-8?q?=3CDM8P223MB0365578F1CE056F4081C563EBAE79=40DM8P223MB0365=2ENAMP2?= =?utf-8?q?23=2EPROD=2EOUTLOOK=2ECOM=3E?= <164932035193.21047.13588447156789154824@lain.red.khirnov.net> =?utf-8?q??= =?utf-8?q?=3CBN0P223MB0358DD034C459B1AD9DAB719BAE99=40BN0P223MB0358=2ENAMP2?= =?utf-8?q?23=2EPROD=2EOUTLOOK=2ECOM=3E?= Mail-Followup-To: FFmpeg development discussions and patches Date: Mon, 11 Apr 2022 10:28:56 +0200 Message-ID: <164966573624.21047.5872909837014503123@lain.red.khirnov.net> User-Agent: alot/0.8.1 MIME-Version: 1.0 Subject: Re: [FFmpeg-devel] [RFC] Switching ffmpeg.c to a threaded architecture 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: Quoting Soft Works (2022-04-08 17:27:10) > > Furthermore, remember that this is just the first step. There will be > > further patchsets converting the other components. I intend to > > upstream > > them gradually one after the other. Your suggestion would require me > > to > > instead write the whole thing at once, fighting rebase conflicts all > > the > > way, and then submit it as a giant utterly unreviewable patchset. > > That's not what I meant, but anyway it's not worth discussing when > it's a minority opinion. > > Just a practical question instead for planning purposes: > > Which timeframe do you expect for the whole process? > When do you plan to start If you mean "start pushing the patches", then I intend to do that as they are reviewed and approved. I hope to send the upstreamable version of this set this week, if nobody has strong objectsions then I might push it after vacation, i.e. late April/early May. > and for how long do you think it will take until all further patchsets > will be submitted/applied? This is very hard to estimate accurately. A pessimistic guess assuming I get stuck on every stupid thing would be end of this year, but I hope for things to go much faster. -- Anton Khirnov _______________________________________________ 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".