Rui Miguel Silva Seabra wrote:
[..]
Yes, indeed you can choose between the two licenses, but you CANNOT
*REMOVE* either of them. Only the Copyright holder who put that license
on it can remove them. This is also what both the GPL and BSD/ISC
licenses state very clearly.
Because of the choice between licenses you can either choose to adhere
to the GPL (thus forcing you to open up your changes) or alternatively
you can choose the BSD and either give your patches back or not.
Still, you can't remove either of the licenses, you have to pass on the
rights you have gotten from the original copyright holder down to
anybody else you are giving this too. And especially if you would be
giving the file down to the author only under GPL your are limiting
their freedom, which is not the intent of the original copyright holder
and also something you fortunately can't be doing.
If you don't like the licensing, then don't use the code at all, don't
even look at it.
Greets,
Jeroen
[demime 1.01d removed an attachment of type application/pgp-signature which had a name of signature.asc]
| David Miller | Re: [PATCH] Stop pmac_zilog from abusing 8250's device numbers. |
| Andrew Morton | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg Kroah-Hartman | [PATCH 010/196] Chinese: add translation of Codingstyle |
| Jan Engelhardt | intel iommu (Re: -mm merge plans for 2.6.23) |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| David Miller | Re: [GIT]: Networking |
| Jarek Poplawski | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Felix von Leitner | socket api problem: can't bind an ipv6 socket to ::ffff:0.0.0.0 |
git: | |
