Linked by Thom Holwerda on Tue 24th Mar 2009 18:02 UTC, submitted by google_ninja
Permalink for comment 354837
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
More News »
Sponsored Links



Member since:
2005-07-06
Actually, the OP isn't entirely wrong.
All versions of the GPL contain a paragraph which specifically states that, if no explicit statement is made as to which version of the GPL applies to the code, *any* version can be taken to apply - including future versions which haven't been written yet.
If you just write a piece of software and stick a copy of the GPL in the archive, no matter what particular version of the GPL that file you put in the archive was, anyone can pick any version of the GPL to apply to your code. This isn't exactly what the OP said - later versions don't supersede earlier ones in this case, so you're still free to apply GPLv2 to any code without a specific GPLv3 statement - but it's not what you said, either.
If you want a particular version or combination of versions of the GPL or LGPL, and *only* those versions, to apply to your code, this has to be explicitly stated.