On Sun, 21 Jul 2013 18:18:17 +0400, Stas Sergeev <s...@list.ru> wrote: > 21.07.2013 15:24, Stephen Kitt пишет: > > Basically you can have one license for a project as a whole, which doesn't > > necessarily match the licenses used in individual sources files, > A correction: it _does_ match the individual source files... some > of them. There are multiple licenses applied, "GPLv2 or later" is > among them, and always was.
Yep, I was speaking generally: any project can have once license for itself as a whole, etc. > > IANAL and all the rest, but as I understand it it could be useful for you > > to change the project license, since that would reduce the "risk" of new > > code being submitted under GPLv2-only, but you won't be able to add GPLv3 > > code until all the GPLv2-only code has been relicensed or rewritten. > Yes, that's exactly what I've done: marked all the old files as > "GPLv2 only", changed the "default" (ie the license for new code) > to "GPLv2 or later" and am expecting this to reduce the risk of > having more of the "GPLv2 only" code in. Indeed. My main point was that you can't add GPLv3 code to the mix as long as there is GPLv2-only code. Regards, Stephen ------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk _______________________________________________ Dosemu-devel mailing list Dosemu-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dosemu-devel
