From: Michael Niedermayer <michael@niedermayer.cc> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [ANNOUNCEMENT] almpeg Date: Mon, 26 May 2025 22:59:45 +0200 Message-ID: <20250526205945.GW29660@pb2> (raw) In-Reply-To: <DM8P223MB03651100FBEA73891C99319ABA65A@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> [-- Attachment #1.1: Type: text/plain, Size: 1168 bytes --] Hi sw On Mon, May 26, 2025 at 05:56:06PM +0000, softworkz . wrote: [...] > > But i certainly was and am open to talk with paul. > > I'd make at least an attempt before going the hard way. I intended to wait for him to contact me, but sure ill mail him first then > > > > > And when you really need something, you can still cherry-pick it anyway. > > > > but we dont really contaminate anything with GPL code > > Okay, so if all this will just remain in "almpeg" with GPL - what's the > benefit? > He appears to be updating regularly from FFmpeg, so if I would want > FFmpeg + his work under GPL - then I could use his project directly - no? in what you write, replce GPL by LGPL as in: > He appears to be updating regularly from FFmpeg, so if I would want > FFmpeg + his work under LGPL - then I could use his project directly - no? I mean, you seem to think this argument doesnt work if the license is LGPL why would it be different with the GPL? thx [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB There will always be a question for which you do not know the correct answer. [-- Attachment #1.2: signature.asc --] [-- Type: application/pgp-signature, Size: 195 bytes --] [-- Attachment #2: Type: text/plain, Size: 251 bytes --] _______________________________________________ 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-05-26 20:59 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-05-25 19:22 Michael Niedermayer 2025-05-25 22:29 ` Kieran Kunhya via ffmpeg-devel 2025-05-25 23:11 ` compn 2025-05-26 8:00 ` Rémi Denis-Courmont 2025-05-26 9:27 ` softworkz . 2025-05-26 11:26 ` Rémi Denis-Courmont 2025-05-26 11:44 ` softworkz . 2025-05-26 11:37 ` Michael Niedermayer 2025-05-26 11:49 ` softworkz . 2025-05-26 12:21 ` softworkz . 2025-05-26 17:21 ` Michael Niedermayer 2025-05-26 17:56 ` softworkz . 2025-05-26 20:59 ` Michael Niedermayer [this message] 2025-05-26 21:10 ` softworkz . 2025-05-26 21:35 ` softworkz . 2025-05-26 21:56 ` softworkz . 2025-05-26 16:36 ` Michael Niedermayer 2025-05-28 1:09 ` Michael Niedermayer
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=20250526205945.GW29660@pb2 \ --to=michael@niedermayer.cc \ --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