RFH: GPLv3

[Michael Eager]

Krzysztof Halasa wrote:
> Michael Eager <eager@eagercon.com> writes:
> 
>> Unfortunately, as I understand it, this is not the case.  If you
>> apply a GPLv3 patch to a previously GPLv2 branch after August 1, then
>> this entire branch, and all files in it, magically and silently
>> becomes GPLv3.  (This is unless FSF agrees with Mark's proposal
>> to dual license patches.)
> 
> I hope the COPYING or similar file will contain the licence text
> under which the code is distributed?

Not until someone updates the txt.  Which should happen quickly,
but if someone applies a GPLv3 patch to a previously GPLv2 branch,
the entire branch becomes GPLv3, whether the COPYING file was
updated or not.

-- 
Michael Eager	 eager@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306  650-325-8077