[ snip ]Linus Torvalds wrote:
[ snip ]
One thing that would make that easier in the future is if contributers
at least started to dual-license their submissions. I.e. if instead
of "GPL version 2", one could say "GPL version 2 or GPL version 3".
It isn't the same thing as the problematic "GPL version 2 or later",
because the developer is not agreeing to an unseen license (GPLv4,
etc). What it does do is make it easier to move to GPLv3 a few years
from now, if that is decided then, as a significant fraction of the
code will already be GPLv3 compatible. That way, if a reason is ever
found to move to v3, at least some of the work will already be done.
- Jim Bruce
-
| Srivatsa Vaddagiri | containers (was Re: -mm merge plans for 2.6.23) |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Benjamin Herrenschmidt | Re: [PATCH] Remove process freezer from suspend to RAM pathway |
git: | |
| Jarek Poplawski | [PATCH take 2] pkt_sched: Protect gen estimators under est_lock. |
| David Miller | [GIT]: Networking |
| Gerhard Pircher | 3c59x: shared interrupt problem |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
