Hello,

Thank you Thomas for the reviews and support!

The proposed actions, by Nicolas George in
https://ffmpeg.org/pipermail/ffmpeg-devel/2017-December/223072.html, were
taken.

>* Can one simply change the tinterlace from GPL to LGPL?
*
Of course not. There are two non-simple courses of action to achieve it:

- Get the approval of all copyright holders. It has been done in the
  past for other filters.

- Remove the GPL tinterlace and at the same time add a new LGPL filter
  that does the same thing and is also called tinterlace.


Only two contributors approved until now, Thomas Mundt and Stefano
Sebatini, while Baptiste Coudurier and Michael Zucchi could not be reached.
Also, the new implementation supports all the features from the old
tinterlace and conditionally (at compile time) the same ASM optimizations
are used, but only if CONFIG_GPL is defined.

Is there any way we can proceed with this patch?

Best regards.


On Fri, Aug 17, 2018 at 5:24 PM, Thomas Mundt <tmund...@gmail.com> wrote:

> Hi,
>
> 2018-08-16 13:56 GMT+02:00 Vasile Toncu <vasile.to...@tremend.com>:
>
> > Hi,
> >
> > Thank you for the additional testing effort.
> > Fixed the issue.
> >
> >
> thanks, the patch looks good to me as far as I can judge.
> It´s up to more experienced developers now to permit the license change.
> Can anybody please have a look at this.
>
> Regards,
> Thomas
> _______________________________________________
> ffmpeg-devel mailing list
> ffmpeg-devel@ffmpeg.org
> http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Reply via email to