From: "Linus Torvalds" <[email protected]>
Exactly. The GPLv3 can _only_ take over a GPLv2 project if the "or later"
exists.
It should also be pointed out that even a "GPLv2 or later" project can be
forked two different ways: you can turn it into a "GPLv3" (with perhaps a
"or later" added too) project, but you can _equally_ turn it into a "GPLv2
only" project.
In other words, even if the license says "GPLv2 or later", the GPLv3 isn't
actually "stronger". The original author dual-licensed it, and expressly
told you that he's ok with any GPL version greater than or equal to 2.
And if it is dual licensed and the user gets to pick the license what
does it mean to have GPLv3 as part of an OR clause? Those who would use
or reuse the code can ignore the GPLv3 part and go forward as GPLv2.
The intent of "GPLv2 or later" might have been "latest GPL version".
But that is not what the words rather explicitly declare.
{^_-} Joanne
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
