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 B2B2540A1A for ; Fri, 4 Mar 2022 18:09:28 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 7BE1268B0FD; Fri, 4 Mar 2022 20:09:25 +0200 (EET) Received: from relay9-d.mail.gandi.net (relay9-d.mail.gandi.net [217.70.183.199]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 578B168B02F for ; Fri, 4 Mar 2022 20:09:18 +0200 (EET) Received: from localhost (213-47-68-29.cable.dynamic.surfer.at [213.47.68.29]) (Authenticated sender: michael@niedermayer.cc) by mail.gandi.net (Postfix) with ESMTPSA id 5CE1DFF805 for ; Fri, 4 Mar 2022 18:09:17 +0000 (UTC) Date: Fri, 4 Mar 2022 19:09:16 +0100 From: Michael Niedermayer To: FFmpeg development discussions and patches Message-ID: <20220304180916.GD2829255@pb2> References: <20220217144904.158764-1-markg85@gmail.com> <20220217144904.158764-2-markg85@gmail.com> <9d46b2e33342cef9793b1c71fb5a60aac9108ea1.camel@acc.umu.se> <20220301220134.GX2829255@pb2> MIME-Version: 1.0 In-Reply-To: Subject: Re: [FFmpeg-devel] [PATCH v8 1/1] avformat: Add IPFS protocol support. 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="===============7211618453935368707==" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: --===============7211618453935368707== Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="YxteXTuy2js5EVGG" Content-Disposition: inline --YxteXTuy2js5EVGG Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Mar 03, 2022 at 03:58:53PM +0100, Mark Gaiser wrote: > On Tue, Mar 1, 2022 at 11:01 PM Michael Niedermayer > wrote: >=20 > > On Mon, Feb 28, 2022 at 02:09:15PM +0100, Tomas H=E4rdin wrote: > > > s=F6n 2022-02-27 klockan 15:29 +0100 skrev Mark Gaiser: > > > > Ping 2.... > > > > > > > > I'd really like to get this merged! > > > > This kinda blocks me right now from proceeding with IPFS integration > > > > in > > > > Kodi, MPV and VLC. Implementations in those (who rely on ffmpeg) are > > > > significantly easier once this patch is finally landed in ffmpeg. > > > > > > I'd like to hear at least one other dev chime in on this one > > > > what exactly are you not sure about ? > > what exactly needs a 2nd look ? > > >=20 > My assumption. > In general just a second look by someone other than Tomas. > And, as he was skeptical about this patch at first, likely another opinion > if this makes sense to add in ffmpeg. > To me it does very much but i'm biased :) ipfs support makes sense to be added to ffmpeg. ive seen ipfs urls and ive already been annoyed that some tools dont "just" work with them. While if i compare this to many other formats which i have never seen outside the context of FFmpeg. So from this biased single sample that i am, ipfs seems more widespread and thats why iam in favor of its support thx [...] --=20 Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Everything should be made as simple as possible, but not simpler. -- Albert Einstein --YxteXTuy2js5EVGG Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iF0EABEIAB0WIQSf8hKLFH72cwut8TNhHseHBAsPqwUCYiJVyAAKCRBhHseHBAsP q99MAJ9+iuMOvDSbLiBckOmQeHXzqq58/QCfdNqOQ9SCb0hyswqInWZxrPjlHbU= =R2ws -----END PGP SIGNATURE----- --YxteXTuy2js5EVGG-- --===============7211618453935368707== 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". --===============7211618453935368707==--