From: compn <ff@hawaiiantel.net>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [RFC] Cherry picks vs merges
Date: Sun, 1 Jun 2025 09:48:20 -1000
Message-ID: <20250601094820.000078cf@hawaiiantel.net> (raw)
In-Reply-To: <20250601192320.GV29660@pb2>
On Sun, 1 Jun 2025 21:23:20 +0200, Michael Niedermayer wrote:
> Hi James
>
> On Sun, Jun 01, 2025 at 02:27:37PM -0300, James Almer wrote:
> > On 6/1/2025 12:22 PM, Michael Niedermayer wrote:
> > > Hi all
> > >
> > > almpeg is now merged upto 1 months ago. (and since last merge it contains
> > > bits of AGPL code)
> > >
> > > The question now is, how does the community want to proceed from here?
> > Full stop.
> >
>
> > Not only you're trying to bypass explicit a license notice on
> > technicalities,
>
> Code is either under the LGPL license or it is not.
> It cannot be sometimes under the LGPL license, the license headers
> on the files in question, distrinbuted by Paul are unmodified
> LGPL headers. There is no extra notice or anything in these headers.
>
> If paul wants them to be GPL he can change these headers at any time.
>
> And the "explicit license notice" you refer to is this:
>
> "All Librempeg modifications, and any new files not available in FFmpeg, are licensed under GPL v2,
> unless stated otherwise."
>
> And it IS stated otherwise in these files by the license header in these
> files.
yes, see for example baptiste's ffmbc fork where he explicitly changed
the license in all files to GPLv2 https://github.com/bcoudurier/FFmbc
Also, please everyone, stop speaking for Paul and let him speak for
himself. if he wants to.
Developers leave, come back, and leave again. its a project made up of
volunteers. No one is forced to join and forced to stay forever.
-compn
_______________________________________________
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-01 19:48 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-01 15:22 Michael Niedermayer
2025-06-01 17:12 ` Kieran Kunhya via ffmpeg-devel
2025-06-01 17:27 ` James Almer
2025-06-01 19:23 ` Michael Niedermayer
2025-06-01 19:48 ` compn [this message]
2025-06-01 20:01 ` James Almer
2025-06-01 21:31 ` Michael Niedermayer
2025-06-02 4:46 ` Vittorio Giovara
2025-06-02 15:05 ` Michael Niedermayer
2025-06-02 7:41 ` Marton Balint
2025-06-02 8:23 ` softworkz .
2025-06-02 15:28 ` Michael Niedermayer
2025-06-02 15:57 ` Kieran Kunhya via ffmpeg-devel
2025-06-04 15:20 ` compn
2025-06-01 21:55 ` Kieran Kunhya via ffmpeg-devel
2025-06-02 4:36 ` Baptiste Coudurier
2025-06-02 15:38 ` Rémi Denis-Courmont
2025-06-03 13:09 ` Michael Niedermayer
2025-06-03 22:38 ` Kieran Kunhya via ffmpeg-devel
2025-06-04 14:51 ` Michael Niedermayer
2025-06-04 15:00 ` Kieran Kunhya via ffmpeg-devel
2025-06-04 15:35 ` Rémi Denis-Courmont
2025-06-04 18:06 ` Tomas Härdin
2025-06-04 20:42 ` Baptiste Coudurier
2025-06-04 22:41 ` 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=20250601094820.000078cf@hawaiiantel.net \
--to=ff@hawaiiantel.net \
--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