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 04416450F0 for ; Mon, 6 Feb 2023 08:46:31 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 5E78A68BE21; Mon, 6 Feb 2023 10:46:28 +0200 (EET) Received: from mailout1.w1.samsung.com (mailout1.w1.samsung.com [210.118.77.11]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id A89B168B461 for ; Mon, 6 Feb 2023 10:46:22 +0200 (EET) Received: from eucas1p2.samsung.com (unknown [182.198.249.207]) by mailout1.w1.samsung.com (KnoxPortal) with ESMTP id 20230206084618euoutp01b11c422fdcdf633c356f5a77df7c4d01~BL_C9KGLr2769927699euoutp01a for ; Mon, 6 Feb 2023 08:46:18 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 mailout1.w1.samsung.com 20230206084618euoutp01b11c422fdcdf633c356f5a77df7c4d01~BL_C9KGLr2769927699euoutp01a DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=samsung.com; s=mail20170921; t=1675673178; bh=DkgEyMBUS7JA3q6QiX5pJ82C4bNO0TrQ97G4CgNkQ/c=; h=From:To:In-Reply-To:Subject:Date:References:From; b=uH27yvRUpVkw0H5vP3/9UOMSfM7Bk6SirXp/09PdpT9trAbf9eTEPzlvODuZjF321 UTnTtt17Y/yuI0Aq/5wJbQfXu6jfFeUojrnscIn0mH6+iI9M70eN0a5ew0cNC21sa4 GBxZrJOkT4knIJXuzHGHcVCuyZG96/qqIHtDaYPg= Received: from eusmges2new.samsung.com (unknown [203.254.199.244]) by eucas1p1.samsung.com (KnoxPortal) with ESMTP id 20230206084618eucas1p15b25f8f1d47b66a785445b3e3c04a9ad~BL_CyJ7UU3008930089eucas1p13 for ; Mon, 6 Feb 2023 08:46:18 +0000 (GMT) Received: from eucas1p1.samsung.com ( [182.198.249.206]) by eusmges2new.samsung.com (EUCPMTA) with SMTP id 8C.14.13597.A5EB0E36; Mon, 6 Feb 2023 08:46:18 +0000 (GMT) Received: from eusmtrp1.samsung.com (unknown [182.198.249.138]) by eucas1p1.samsung.com (KnoxPortal) with ESMTPA id 20230206084618eucas1p1035ada33f30a25d87f8199ce57a9a54a~BL_CbsBPN1574215742eucas1p1i for ; Mon, 6 Feb 2023 08:46:18 +0000 (GMT) Received: from eusmgms2.samsung.com (unknown [182.198.249.180]) by eusmtrp1.samsung.com (KnoxPortal) with ESMTP id 20230206084618eusmtrp17150e7153a812bf1657199fd28023ac7~BL_CbK33f2102121021eusmtrp1f for ; Mon, 6 Feb 2023 08:46:18 +0000 (GMT) X-AuditID: cbfec7f4-207ff7000000351d-a1-63e0be5a52f1 Received: from eusmtip1.samsung.com ( [203.254.199.221]) by eusmgms2.samsung.com (EUCPMTA) with SMTP id FA.73.00518.95EB0E36; Mon, 6 Feb 2023 08:46:18 +0000 (GMT) Received: from AMDN5164 (unknown [106.210.132.171]) by eusmtip1.samsung.com (KnoxPortal) with ESMTPA id 20230206084617eusmtip1067255b853bc46cfb43c9860527f1fb5~BL_CN429s0452004520eusmtip1O for ; Mon, 6 Feb 2023 08:46:17 +0000 (GMT) From: "Dawid Kozinski/Multimedia \(PLT\) /SRPOL/Staff Engineer/Samsung Electronics" To: "'FFmpeg development discussions and patches'" In-Reply-To: Date: Mon, 6 Feb 2023 09:46:17 +0100 Message-ID: <01b601d93a07$7a83f270$6f8bd750$@samsung.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 16.0 Thread-Index: AQHfTkAD05xhnXzFRoOue/OS8+U6MgHIBH+EAjuD4hgCxQbjjwJzgaeCAwHQ8ngCFCnfCACs5nZaAiq4hy0CgDcQrwK1e3Q3AbSPh3+t9M2o0A== Content-Language: pl X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrJIsWRmVeSWpSXmKPExsWy7djPc7pR+x4kG1x+LGzx7dMZZgdGjz+L NrMEMEZx2aSk5mSWpRbp2yVwZZxecYSt4JJyRefSV+wNjHuUuhg5OSQETCSWv3jC0sXIxSEk sIJR4s+nyUwQziQmiRkrmqGciUwSh7oXs8K03D3+gBEisZxRYs+qiWwQThuTxP2Xd9lAqtgE 8iQef17LDGKLCPhIdK9fD9bNKaAicXvVQrAaYYFUiWOdV4GWc3CwAMWXrDMCCfMKWErc6rjB CGELSpycCXIfJwezgJ7Es1OzoGxtiWULXzNDHKQg8fPpMlaQMSICdRLPdzFBlIhI3HjUAnan hMBEDom/E96wQdS7SKzZfZMJwhaWeHV8CzuELSNxenIP2DkSAsUSh/odIMwaiUM/0iEqrCXe Nh5nhLAdJY5O7WKGKOGTuPFWEGIrn8SkbdOhwrwSHW1CEKaKRF+nGESjlMTTZXOYJzAqzULy 4SwkH85C8uEsJK8sYGRZxSieWlqcm55abJSXWq5XnJhbXJqXrpecn7uJEZgaTv87/mUH4/JX H/UOMTJxMB5ilOBgVhLhXX76TrIQb0piZVVqUX58UWlOavEhRmkOFiVxXm3bk8lCAumJJanZ qakFqUUwWSYOTqkGps22PtG13LXb3vqtbmE5umbL3oXGX9Ynb9Vruhth91Jg6QqVeZUX33Uu PfvucvznhNxrnFcVdrOGRUk5dnFMmru0QeGJ4/1DDfkrWo9FKycYGDwPCJOfk/aZQ+18/FVu /bQ2ta4c3mM27Ze9q/OWuXNZ2hjcW/v6TfIe8Rs3F3LLcK3nKkoKDW19arft87apna8N7y5b 4vUlyXfdyQML/aMvzWbUYjPhMJz7wuiXvuiKbR2Mi4z1Z9sEalwWijDU3xbDPL/lffK9vcbu CWnHsjOrc3a8XFN8o+fYgqhtjz6tU9nfcrerpftxR2Co1JwpEv2KAT7PorV2HDZYfzXh5+U5 /ScMNoios8d7+chNU2Ipzkg01GIuKk4EAAlwhdV8AwAA X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrHLMWRmVeSWpSXmKPExsVy+t/xu7pR+x4kG7QcYbL49ukMswOjx59F m1kCGKP0bIryS0tSFTLyi0tslaINLYz0DC0t9IxMLPUMjc1jrYxMlfTtbFJSczLLUov07RL0 Mpbdus9YcF6yYuOCHcwNjFdFuhg5OSQETCTuHn/A2MXIxSEksJRR4lfvRHaIhJTE0qWLGCFs YYk/17rYIIpamCSap69jAUmwCeRIrJ09kQnEFhHwkehev54VougDs8TalydZQRKcAioSt1ct ZAOxhQWSJR7cWgjUzMHBAhRfss4IJMwrYClxq+MGI4QtKHFy5hOw+cwCBhJLFv5igrC1JZYt fM0McZCCxM+ny1hBxogI1Ek83wVVIiJx41EL4wRGoVlIJs1CMmkWkkmzkLQsYGRZxSiSWlqc m55bbKRXnJhbXJqXrpecn7uJERgR24793LKDceWrj3qHGJk4GA8xSnAwK4nwLj99J1mINyWx siq1KD++qDQntfgQoynQZxOZpUST84ExmVcSb2hmYGpoYmZpYGppZqwkzutZ0JEoJJCeWJKa nZpakFoE08fEwSnVwLSqPL/vt32oyBHrdmcH7yPFHw2sJn5qb+KKiNt7UsA2efLDpdfn6uno /2hbura50/6ynnPNRZ+Fsw8cNBBgFfC4cnrNFhmfS0+CPy+tOZb/unjDqU9eLZJzK3dfkb6y +4/PkZqlC666/ZsVLc81pVNfQMXdwSpKUPOtudndGnnXrQcnZM/uubdn+yJJe2uemY3h83hS 6s58PBoi3hpRsG7tDubpuYZ6H082mFTOcw/wMy5bZyfV3VvN8rV4sfrGrBbu23rT+uQPy7bv ZnArP7Ch0W7L6w8qzSsyHS42WKRPqbM5vPSD3ptra7vumaitrHA68nfb1I7ieakRd7MOWy3+ WTih66+BvuRjdUfmM0osxRmJhlrMRcWJAFT3Bh4RAwAA X-CMS-MailID: 20230206084618eucas1p1035ada33f30a25d87f8199ce57a9a54a X-Msg-Generator: CA X-RootMTR: 20230129231836eucas1p2a51c791cf026add6503cfcf7ec69c787 X-EPHeader: CA CMS-TYPE: 201P X-CMS-RootMailID: 20230129231836eucas1p2a51c791cf026add6503cfcf7ec69c787 References: <20221027164524.GL4048421@pb2> <003b01d90eed$852039e0$8f60ada0$@samsung.com> <20221214213607.GN3806951@pb2> <00c001d91065$a9d7be10$fd873a30$@samsung.com> <20221215192239.GQ3806951@pb2> <003401d93247$4d542fd0$e7fc8f70$@samsung.com> <20230129095713.GI1949656@pb2> Subject: Re: [FFmpeg-devel] [PATCH v14 9/9] avcodec/evc: Changes in Changelog and MAINTAINERS files 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="iso-8859-2" Content-Transfer-Encoding: quoted-printable Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: Michael, could you review Lynne's policy change on maintainership? It's essential for us to move EVC case one step forward. -----Original Message----- From: ffmpeg-devel On Behalf Of Lynne Sent: poniedzia=B3ek, 30 stycznia 2023 00:18 To: FFmpeg development discussions and patches Subject: Re: [FFmpeg-devel] [PATCH v14 9/9] avcodec/evc: Changes in Changelog and MAINTAINERS files Jan 29, 2023, 10:57 by michael@niedermayer.cc: > Hi > > On Fri, Jan 27, 2023 at 01:03:00PM +0100, Dawid Kozinski/Multimedia (PLT) /SRPOL/Staff Engineer/Samsung Electronics wrote: > >> Hi, >> It's been almost a month since we submitted our latest changes to the FFmpeg patchwork. I know that EVC implementation isn't the only thing you are working on at the moment but we'd like to do another step forward, toward merging our implementation into the master branch of the FFmpeg repository. = >> The contribution is something that we take seriously so we'd like to finally do some progress. >> We would like to merge it as soon as it is enough good and it meets the expected quality. Continual synchronization of our changes with the latest FFmpeg changes and splitting our changes into patches is, let's say a painstaking job. It would be much easier to develop and refine the code if we could skip that hard splitting on patches step that we have to do each time we do any, even small change. >> We know that the new FFmpeg version will be released soon and you may be absorbed and overwhelmed with the work related to the new release. However, we'd be grateful if you found a little time and take a look at our latest changes. >> Last but not least. Do you have any plans related to including such changes as our EVC implementation in the next release? >> > > I cannot speak for others but ATM for me its difficult to add this = > patchset to my todo list. If someone reviews and applies it it could = > make it in for the release but will anyone, i do not know. > What i can say is that if a patch which adds you to MAINTAINERS is = > applied ping me and ill give you git write (unless there are some new = > standing objections), and once you have that you can work on this code with less pain. > But i will leave applying the MAINTAINERS change to others too as some = > people seemed not happy anout it and i think in such case its better = > if a 2nd developer does that > > PS: Maybe you can troll the people who didnt like your MAINTAINERS = > addition into reviewing & applying your patchset. Its not an = > unreasonable request because if you dont have git write someone else = > has to apply changes > I assign myself to personally review the patchset and push it, if you review my policy change on maintainership. As I said, I have no objection on who gets maintainership, just that it is done explicitly via a separate list in the maintainers file. _______________________________________________ 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". _______________________________________________ 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".