From: Adrian Bunk <bunk-cg1h10c7RbKzQB+pC5nmwQ@public.gmane.org>
To: "Grover, Andrew" <andrew.grover-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: acpi-devel-pyega4qmqnRoyOMFzWx49A@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Proposed ACPI Licensing change
Date: Sat, 7 Dec 2002 01:24:06 +0100 [thread overview]
Message-ID: <20021207002405.GR2544@fs.tum.de> (raw)
In-Reply-To: <EDC461A30AC4D511ADE10002A5072CAD04C7A57F-OU+JdkIUtvd9zuciVAfUoVDQ4js95KgL@public.gmane.org>
On Fri, Dec 06, 2002 at 04:10:00PM -0800, Grover, Andrew wrote:
> Hi all,
Hi Andrew,
>...
> One consequence of this is that we have not been able to benefit directly
> from patches from other Linux contributors. The reason is, patches submitted
> to code only under the GPL must also be GPL, and therefore we cannot take
> them directly and still make our code available under a license other than
> the GPL. (We have to determine the problem the patch fixes and then do the
> fix ourselves.)
>...
> In order to solve this, we are considering releasing the Linux version of
> the interpreter under a dual license. This would allow direct incorporation
> of changes. Any patches submitted against the ACPI core code would
> implicitly be allowed to be used by us in a non-GPL context. This is already
> done elsewhere in the Linux kernel source by the PCMCIA code, for example.
>
> Comments?
two comments regarding the right of an author to freely choose under
which license(s) he wants to make his patch available:
If a submitter wants to allow you to use his patch under both licenses
he's already able to allow you to do so.
You can't forbid people to send GPL-only patches, so if a person doesn't
want his patch under your looser license you can't enforce that he also
releases it under your looser license.
> Regards -- Andy
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
WARNING: multiple messages have this Message-ID (diff)
From: Adrian Bunk <bunk@fs.tum.de>
To: "Grover, Andrew" <andrew.grover@intel.com>
Cc: acpi-devel@sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: Proposed ACPI Licensing change
Date: Sat, 7 Dec 2002 01:24:06 +0100 [thread overview]
Message-ID: <20021207002405.GR2544@fs.tum.de> (raw)
In-Reply-To: <EDC461A30AC4D511ADE10002A5072CAD04C7A57F@orsmsx119.jf.intel.com>
On Fri, Dec 06, 2002 at 04:10:00PM -0800, Grover, Andrew wrote:
> Hi all,
Hi Andrew,
>...
> One consequence of this is that we have not been able to benefit directly
> from patches from other Linux contributors. The reason is, patches submitted
> to code only under the GPL must also be GPL, and therefore we cannot take
> them directly and still make our code available under a license other than
> the GPL. (We have to determine the problem the patch fixes and then do the
> fix ourselves.)
>...
> In order to solve this, we are considering releasing the Linux version of
> the interpreter under a dual license. This would allow direct incorporation
> of changes. Any patches submitted against the ACPI core code would
> implicitly be allowed to be used by us in a non-GPL context. This is already
> done elsewhere in the Linux kernel source by the PCMCIA code, for example.
>
> Comments?
two comments regarding the right of an author to freely choose under
which license(s) he wants to make his patch available:
If a submitter wants to allow you to use his patch under both licenses
he's already able to allow you to do so.
You can't forbid people to send GPL-only patches, so if a person doesn't
want his patch under your looser license you can't enforce that he also
releases it under your looser license.
> Regards -- Andy
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2002-12-07 0:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-07 0:10 Proposed ACPI Licensing change Grover, Andrew
2002-12-07 0:10 ` Grover, Andrew
[not found] ` <EDC461A30AC4D511ADE10002A5072CAD04C7A57F-OU+JdkIUtvd9zuciVAfUoVDQ4js95KgL@public.gmane.org>
2002-12-07 0:24 ` Adrian Bunk [this message]
2002-12-07 0:24 ` Adrian Bunk
2002-12-07 0:36 ` David Schwartz
[not found] ` <20021207002405.GR2544-cg1h10c7RbKzQB+pC5nmwQ@public.gmane.org>
2002-12-07 0:36 ` David Schwartz
2002-12-07 0:36 ` David Schwartz
2002-12-07 20:07 ` Linus Torvalds
2002-12-09 19:39 ` H. Peter Anvin
2002-12-07 0:51 ` Christoph Hellwig
2002-12-07 0:51 ` Christoph Hellwig
2002-12-07 2:16 ` Alan Cox
2002-12-07 2:16 ` Alan Cox
2002-12-07 9:58 ` Jeff Garzik
2002-12-07 9:58 ` Jeff Garzik
2002-12-07 17:46 ` Greg KH
2002-12-07 17:46 ` Greg KH
2002-12-09 18:59 ` Pavel Machek
2002-12-09 18:59 ` Pavel Machek
2002-12-07 23:44 ` Hans Reiser
-- strict thread matches above, loose matches on Subject: below --
2002-12-07 1:06 Adrian Bunk
2002-12-07 1:06 ` Adrian Bunk
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=20021207002405.GR2544@fs.tum.de \
--to=bunk-cg1h10c7rbkzqb+pc5nmwq@public.gmane.org \
--cc=acpi-devel-pyega4qmqnRoyOMFzWx49A@public.gmane.org \
--cc=andrew.grover-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/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.