From: "chxanders@gmail.com" <chxanders@gmail.com>
To: Chris Samuel <chris@csamuel.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
miaox@cn.fujitsu.com, Ingo Molnar <mingo@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Chris Mason <chris.mason@oracle.com>,
"Theodore Ts'o" <tytso@mit.edu>,
Andreas Dilger <adilger.kernel@dilger.ca>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Linux Btrfs <linux-btrfs@vger.kernel.org>,
Linux Ext4 <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH 1/3] lib: introduce some memory copy macros and functions
Date: Thu, 2 Sep 2010 15:35:53 +0700 [thread overview]
Message-ID: <AANLkTi=8V+3HS-+o=FUbM20ZXZ6mDXb67dOgJiwiJb6y@mail.gmail.com> (raw)
In-Reply-To: <4C7F5F38.3050104@csamuel.org>
On 2 September 2010 15:24, Chris Samuel <chris@csamuel.org> wrote:
> On 02/09/10 18:16, chxanders@gmail.com wrote:
>
>> Umm, isn't the only one that can do that the copyright holder?
>
> The copyright holder can use whatever license they wish; the LGPL
> tells the licensee what rights *they* have, which includes distributing
> the software under the (more strict) GPLv2.
>
Wow, there is even a FAQ.
http://www.gnu.org/licenses/gpl-faq.html#compat-matrix-footnote-7
in the matrix notes 1 and 7 apply, which means that anyone, not just
the license holder may change to GPL v2 from LGPV 2.1
Cheers
Chris
prev parent reply other threads:[~2010-09-02 8:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-01 10:36 [PATCH 1/3] lib: introduce some memory copy macros and functions Miao Xie
2010-09-01 15:25 ` Peter Zijlstra
2010-09-02 5:44 ` Miao Xie
2010-09-02 5:55 ` Chris Samuel
2010-09-02 6:50 ` Miao Xie
2010-09-02 7:07 ` Chris Samuel
2010-09-02 7:55 ` Peter Zijlstra
2010-09-02 7:57 ` Peter Zijlstra
2010-09-02 8:16 ` chxanders
2010-09-02 8:24 ` Chris Samuel
2010-09-02 8:35 ` chxanders [this message]
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='AANLkTi=8V+3HS-+o=FUbM20ZXZ6mDXb67dOgJiwiJb6y@mail.gmail.com' \
--to=chxanders@gmail.com \
--cc=adilger.kernel@dilger.ca \
--cc=akpm@linux-foundation.org \
--cc=chris.mason@oracle.com \
--cc=chris@csamuel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miaox@cn.fujitsu.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tytso@mit.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).