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 E734E43261 for ; Mon, 25 Jul 2022 19:39:27 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 6C94668B7CF; Mon, 25 Jul 2022 22:39:24 +0300 (EEST) Received: from relay5-d.mail.gandi.net (relay5-d.mail.gandi.net [217.70.183.197]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 5888568B73E for ; Mon, 25 Jul 2022 22:39:17 +0300 (EEST) Received: (Authenticated sender: michael@niedermayer.cc) by mail.gandi.net (Postfix) with ESMTPSA id 75F0C1C0006 for ; Mon, 25 Jul 2022 19:39:16 +0000 (UTC) Date: Mon, 25 Jul 2022 21:39:15 +0200 From: Michael Niedermayer To: FFmpeg development discussions and patches Message-ID: <20220725193915.GV2088045@pb2> References: <20220703170714.GF396728@pb2> <20220725113201.GU2088045@pb2> MIME-Version: 1.0 In-Reply-To: Subject: Re: [FFmpeg-devel] [PATCH v5 00/25] Subtitle Filtering 2022 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: multipart/mixed; boundary="===============3226816751344671286==" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: --===============3226816751344671286== Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="Jp4gq2voFtVFKZdE" Content-Disposition: inline --Jp4gq2voFtVFKZdE Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jul 25, 2022 at 09:01:03PM +0200, Nicolas George wrote: [...] > > If we add a XML parser to FFmpeg. Such a thing would be used by several > > bits and we need to ensure it has redundant maintainership. > > So i think a xml parser needs broad support by developers otherwise we > > run the risk that if it has a single maintainer only and that maintainer > > stops maintaining it that could be annoying to more than just the parser > > itself. > > I cannot remember exactly without re-reading the old thread what the is= sues > > people had with the xml parser. If it was some component of it or in ge= neral. > > But i think its mostly a question if theres more than one person who wa= nts > > to maintain it. >=20 > There is nothing to re-read: >=20 > https://ffmpeg.org/pipermail/ffmpeg-devel/2022-May/thread.html#296107 >=20 > Nobody answered. Even to send files to make sure they would be > supported. that says "WIP" in the subject. I think some people when they see WIP they skip it and wait for a final version to review. thx [...] --=20 Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB The real ebay dictionary, page 2 "100% positive feedback" - "All either got their money back or didnt compla= in" "Best seller ever, very honest" - "Seller refunded buyer after failed scam" --Jp4gq2voFtVFKZdE Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iF0EABEIAB0WIQSf8hKLFH72cwut8TNhHseHBAsPqwUCYt7xXwAKCRBhHseHBAsP q5xrAJ9PDr+6NxyKjWjky1RCM1JAzhuJagCfcS2lNk0Q6EH+F9DFURZL6Nt8wmc= =c4ec -----END PGP SIGNATURE----- --Jp4gq2voFtVFKZdE-- --===============3226816751344671286== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ 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". --===============3226816751344671286==--