From: Pavel Machek <pavel@ucw.cz>
To: David Schwartz <davids@webmaster.com>
Cc: pradeep singh rautela <rautelap@gmail.com>,
hjk@linutronix.de, Greg KH <greg@kroah.com>,
linux-kernel@vger.kernel.org
Subject: Re: [Q]Can a file be dual licensed in upstream kernel?
Date: Wed, 14 May 2008 17:28:35 +0200 [thread overview]
Message-ID: <20080514152834.GA6888@ucw.cz> (raw)
In-Reply-To: <MDEHLPKNGKAHNMBLJOLKKEBJMFAC.davids@webmaster.com>
On Thu 2008-05-01 07:59:54, David Schwartz wrote:
>
> > In my _personal_opinion_, dual licensing gives you the right to choose
> > between two licenses.
>
> Dual licensing gives every recipient both licenses from the original author.
> You can choose which license you will obtain rights from.
>
> > If a file is dual licensed BSD/GPLv2, anybody
> > (including yourself) is free to get rid of the BSD part and make it
> > GPLv2 only.
>
> Really? Which license or law gives you the right to change the licensing
> terms on code you didn't write? At least in the United States, you cannot
You don't change licensing. You got choice of two licenses, and you
selected one. GPL gives you right to remove the BSD licensing terms
you did not choose.
(People still can use the code under BSD license _if_ they know it was
originally BSD/GPL.. as long as you don't modify it).
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2008-05-14 15:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-29 5:37 [Q]Can a file be dual licensed in upstream kernel? pradeep singh rautela
2008-04-29 5:53 ` Greg KH
2008-04-29 6:10 ` pradeep singh rautela
2008-04-29 6:26 ` Hans J. Koch
2008-04-29 6:31 ` pradeep singh rautela
2008-05-01 14:59 ` David Schwartz
2008-05-14 15:28 ` Pavel Machek [this message]
2008-05-14 23:36 ` David Schwartz
2008-05-15 18:23 ` Pavel Machek
2008-04-29 6:33 ` Bart Van Assche
2008-04-29 8:50 ` Alan Cox
2008-04-29 9:16 ` pradeep singh rautela
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080514152834.GA6888@ucw.cz \
--to=pavel@ucw.cz \
--cc=davids@webmaster.com \
--cc=greg@kroah.com \
--cc=hjk@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rautelap@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.