Did we ever care about this runtime linking exception stuff? We have
lots of GPL v2 3rd party code, does it all contain this clause?


Am 02.10.2013 10:47, schrieb Aleksey Bragin:
> You are implementing part of ReactOS so you can't just silently
> relicense your code in one commit to a license which is incompatible
> with ReactOS aims and goals.
>
> At the very least, I would appreciate a discussion with our team
> regarding this before doing such commits.
>
> Please revert. The runtime linking exception was added for a reason,
> not for amusement or RMS trolling. RMS is unhappy either way (not that
> I care about his opinion :).
>
> Regards,
> Aleksey Bragin
>
> On 01.10.2013 2:01, [email protected] wrote:
>> Author: aandrejevic
>> Date: Mon Sep 30 22:01:38 2013
>> New Revision: 60485
>>
>> URL: http://svn.reactos.org/svn/reactos?rev=60485&view=rev
>> Log:
>> [SOFT386]
>> Change the license of Soft386 to GPLv2. The previous license was also
>> GPLv2, but it had a runtime linking exception. The new license is the
>> original GPLv2 with no exceptions.
>>
>>
>> Added:
>>      branches/ntvdm/lib/soft386/COPYING   (with props)
>> Modified:
>>      branches/ntvdm/lib/soft386/common.c
>>      branches/ntvdm/lib/soft386/common.h
>>      branches/ntvdm/lib/soft386/common.inl
>>      branches/ntvdm/lib/soft386/opcodes.c
>>      branches/ntvdm/lib/soft386/opcodes.h
>>      branches/ntvdm/lib/soft386/opgroups.c
>>      branches/ntvdm/lib/soft386/opgroups.h
>>      branches/ntvdm/lib/soft386/soft386.c
>>
>
>
> _______________________________________________
> Ros-dev mailing list
> [email protected]
> http://www.reactos.org/mailman/listinfo/ros-dev
>


_______________________________________________
Ros-dev mailing list
[email protected]
http://www.reactos.org/mailman/listinfo/ros-dev

Reply via email to