[FFmpeg-devel] [PATCH 3/5] Renamed reinterlace to tinterlace

[Vasile Toncu]

Hello,

Happy New Year.
Any news about this patch? Maybe Carl Eugen Hoyos could help us with this?

Best regards.

On Thu, Dec 6, 2018 at 6:10 PM Vasile Toncu <vasile.toncu at tremend.com>
wrote:

> Hi,
>
> Since this patch is passing all the current tests, all the modification
> required by Thomas were implemented and from our point of view it satisfies
> all requirements for adding the double license to the filter, please
> approve this patch for integration. Also, there are two more patches
> blocked at the moment. This two patches add new features and improvements
> for the filter.
>
> Thank you. Regards.
>
> On Tue, Oct 16, 2018 at 6:40 PM Vasile Toncu <vasile.toncu at tremend.com>
> wrote:
>
>> Hello,
>>
>> Still Baptiste Coudurier and Michael Zucchi could not be reached, however
>> since the old GPL tinterlace was replaced with a new LGPL implementation
>> aren't we on the second course of action recommended by Nicolas George? And
>> by that means can we change the license of this implementation without the
>> approval of the original contributors whose code was removed?
>> Maybe someone else can have a look at the new implementation and provide
>> the necessary feedback in order to merge this patch and unblock the
>> development of the patches with new functionalities.
>>
>> Thank you.
>> Best regards.
>>
>>
>>
>> On Mon, Sep 17, 2018 at 8:28 AM, Vasile Toncu <vasile.toncu at tremend.com>
>> wrote:
>>
>>> 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 <tmundt75 at gmail.com>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> 2018-08-16 13:56 GMT+02:00 Vasile Toncu <vasile.toncu at 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 at ffmpeg.org
>>>> http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>>>>
>>>
>>>
>>