From: dexuan.cui@intel.com (Cui, Dexuan)
Subject: [ltt-dev] lttng-ust: Inconsistent license info in manual and source code?
Date: Thu, 30 Sep 2010 17:13:35 +0800 [thread overview]
Message-ID: <1865303E0DED764181A9D882DEF65FB65DD2812229@shsmsx502.ccr.corp.intel.com> (raw)
In-Reply-To: <1865303E0DED764181A9D882DEF65FB6521EDABC08@shsmsx502.ccr.corp.intel.com>
Cui, Dexuan wrote:
> Pierre-Marc Fournier wrote:
>> On 08/12/2010 11:51 PM, Cui, Dexuan wrote:
>>> Hi, in the latest release 0.5 of lttng-ust
>>> (http://lttng.org/files/ust/releases/ust-0.5.tar.gz), I found in the
>>> source directory, doc/manual/ust.html says ustctl/libustcmd/ustd are
>>> licensed as GPL v2, but the source codes of ustctl/libustcmd/ustd
>>> have a LGPLv2.1+ header. I checked
>>> git://git.dorsal.polymtl.ca/git/ust.git and it has the same issue.
>>>
>>> Could somebody please clarify the inconsistency? Thanks!
>>
>> The licenses in the file have priority. The manual needs to be
>> updated.
>>
>> pmf
>
> Thanks a lot for the quick clarification! :-)
Hi, today I checked the release of 0.7 and the latest's ust.git. Looks this inconsistency in manual and source cde is still there?
Do we have a plan to fix it?
And, the COPYING only mentions "GPLv2 or any later version", but doesn't mention LGPL at all.
And, the files in ust.git/snprintf/ has a BSD license header.
So, what's the "overall" license of lttng-ust -- "LGPL2.1+ & BSD"?
Could you please clarify my questions? Thanks very much!
Thanks,
-- Dexuan
next prev parent reply other threads:[~2010-09-30 9:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-13 3:51 Cui, Dexuan
2010-08-13 3:56 ` Pierre-Marc Fournier
2010-08-13 4:05 ` Cui, Dexuan
2010-09-30 9:13 ` Cui, Dexuan [this message]
2010-09-30 10:21 ` Nils Carlson
2010-09-30 10:49 ` Cui, Dexuan
2010-09-30 12:01 ` Pierre-Marc Fournier
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=1865303E0DED764181A9D882DEF65FB65DD2812229@shsmsx502.ccr.corp.intel.com \
--to=dexuan.cui@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox