From: "softworkz ." <softworkz-at-hotmail.com@ffmpeg.org> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH WIP 01/10] ffbuild/bin2c: Use zlib directly instead of gzip Date: Tue, 17 Jun 2025 14:35:29 +0000 Message-ID: <DM8P223MB0365E0B03E92BFA7CFCCC007BA73A@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> (raw) In-Reply-To: <aFF3EdUuvcoGsOuR@phare.normalesup.org> > -----Original Message----- > From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of > Nicolas George > Sent: Tuesday, June 17, 2025 4:09 PM > To: FFmpeg development discussions and patches <ffmpeg- > devel@ffmpeg.org> > Subject: Re: [FFmpeg-devel] [PATCH WIP 01/10] ffbuild/bin2c: Use zlib > directly instead of gzip > > softworkz . (HE12025-06-17): > > It's not about replacing zlib in general. The scope is having our own > > compression code for ptx and resource compression only. > > This is what I understood. But obviously you didn't: > If you can write a zlib replacement specifically for FFmpeg with some technical > benefit over other implementations, do so. I didn't talk about a zlib replacement. It is about any kind of compression code, not needing to be zlib compatible at all. > go away. Likewise! sw _______________________________________________ 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".
next prev parent reply other threads:[~2025-06-17 14:35 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-06-02 2:38 Andreas Rheinhardt 2025-06-02 3:22 ` softworkz . 2025-06-02 22:33 ` softworkz . 2025-06-03 14:33 ` Andreas Rheinhardt 2025-06-03 14:47 ` softworkz . 2025-06-11 3:05 ` softworkz . 2025-06-16 18:51 ` Andreas Rheinhardt 2025-06-16 19:15 ` softworkz . 2025-06-16 19:24 ` Andreas Rheinhardt 2025-06-16 20:18 ` softworkz . 2025-06-16 22:15 ` Andreas Rheinhardt 2025-06-17 9:29 ` Nicolas George 2025-06-17 13:23 ` softworkz . 2025-06-17 14:09 ` Nicolas George 2025-06-17 14:35 ` softworkz . [this message] 2025-06-17 14:40 ` Nicolas George 2025-06-17 14:41 ` James Almer 2025-06-17 14:51 ` softworkz . 2025-06-18 7:09 ` Nicolas George
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=DM8P223MB0365E0B03E92BFA7CFCCC007BA73A@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM \ --to=softworkz-at-hotmail.com@ffmpeg.org \ --cc=ffmpeg-devel@ffmpeg.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel This inbox may be cloned and mirrored by anyone: git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \ ffmpegdev@gitmailbox.com public-inbox-index ffmpegdev Example config snippet for mirrors. AGPL code for this site: git clone https://public-inbox.org/public-inbox.git