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]
Message-ID: <orzm326s3w.fsf@oliva.athome.lsd.ic.unicamp.br>
Date:	Thu, 14 Jun 2007 20:20:19 -0300
From:	Alexandre Oliva <aoliva@...hat.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Sean <seanlkml@...patico.ca>, Adrian Bunk <bunk@...sta.de>,
	Valdis.Kletnieks@...edu, Daniel Hazelton <dhazelton@...er.net>,
	Alan Cox <alan@...rguk.ukuu.org.uk>, Greg KH <greg@...ah.com>,
	debian developer <debiandev@...il.com>, david@...g.hm,
	Tarkan Erimer <tarkan@...one.net.tr>,
	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>, mingo@...e.hu
Subject: Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3

On Jun 14, 2007, Linus Torvalds <torvalds@...ux-foundation.org> wrote:

> On Thu, 14 Jun 2007, Alexandre Oliva wrote:
>> 
>> Hmm...  So, if someone takes one of the many GPLv2+ contributions and
>> makes improvements under GPLv3+, you're going to make an effort to
>> accept them, rather than rejecting them because they're under the
>> GPLv3?

> You *cannot* make GPLv3-only contributions to the kernel.

I can make improvements to GPLv2+ files under GPLv3 (or rather will,
after GPLv3 is published).  And you wrote:

> I want to be able to use other peoples improvements. If they release
> improved versions of the software I started, I want to be able to
> merge those improvements if I want to.

So which is it?  Do you want to be able to use other people's
improvements, respecting the conditions you said they are legitimately
entitled to make, or is this not quite the whole story?

> But not within the confines of the Linux kernel. Within the Linux kernel, 
> the GPLv2 rules - and "GPLv2+" becomes just "GPLv2", since the GPLv3 is 
> not compatible with v2.

I understand this very well.  You'd have to get the kernel upgraded to
GPLv3 in order to accept the contribution.

Likewise for any other contribution under any other GPLv2-incompatible
license.

So, you see, your statement above, about wanting to be able to use
other people's improvements, cannot be taken without qualification.

-- 
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