lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 21 Jun 2007 14:53:04 -0300
From:	Alexandre Oliva <aoliva@...hat.com>
To:	jimmy bahuleyan <knight.camelot@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: how about mutual compatibility between Linux's GPLv2 and GPLv3?

On Jun 21, 2007, jimmy bahuleyan <knight.camelot@...il.com> wrote:

> There, that right there, wouldn't it again require a 'nod' from all
> those who have contributed to the kernel (because at the time they did,
> the license was GPLv2 without any additions)?

That's my understanding, yes, but IANAL.


Similarly, any GPLv2 and GPLv3 projects that wish to cooperate with
each other could introduce mutual additional permissions in the way I
suggested, even if neither GPLv2 nor GPLv3 themselves make such
provisions.  This is a decision that copyright holders can make, in
very much the same way that they can make their decisions as to
permitting relicensing under newer versions of the GPL, or even older
versions of the GPL.


BTW, I should probably have made clear that, as usual, I was speaking
my own mind, not speaking on behalf of FSFLA or Red Hat, with whom I'm
associated, and certainly not on behalf of FSF, with whom I'm not
associated.  Just in case this wasn't clear yet ;-)

-- 
Alexandre Oliva         http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member         http://www.fsfla.org/
Red Hat Compiler Engineer   aoliva@...dhat.com, gcc.gnu.org}
Free Software Evangelist  oliva@...d.ic.unicamp.br, gnu.org}
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ