From: fche@redhat.com (Frank Ch. Eigler)
To: Mathieu Desnoyers <compudj@krystal.dyndns.org>
Cc: Ingo Molnar <mingo@elte.hu>,
Christoph Hellwig <hch@infradead.org>,
Pierre-Marc Fournier <pierre-marc.fournier@polymtl.ca>,
Tom Zanussi <tzanussi@gmail.com>,
karim@opersys.com, Michel Dagenais <michel.dagenais@polymtl.ca>,
ltt-dev@lists.casi.polymtl.ca,
Lai Jiangshan <laijs@cn.fujitsu.com>,
kosaki.motohiro@jp.fujitsu.com, linux-kernel@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Robert Wisniewski <bob@watson.ibm.com>
Subject: Re: Dual-licensing LTTng, marker and tracepoints under GPLv2+/LGPLv2.1+
Date: Wed, 24 Jun 2009 12:33:00 -0400 [thread overview]
Message-ID: <y0mprctzj5v.fsf@fche.csb> (raw)
In-Reply-To: <20090624141438.GA15420@Krystal> (Mathieu Desnoyers's message of "Wed, 24 Jun 2009 10:14:39 -0400")
Mathieu Desnoyers <compudj@krystal.dyndns.org> writes:
> [...] The goal we pursue by dual-licensing with GPLv2/LGPLv2.1 is
> to permit instrumented applications to be themselves distributed
> under other license than GPL. [...]
Is there some reason you can't just fork/copy off some earlier version
of these files over which you had sole authorship (if any)?
> [...]The goal is to permit this library, which includes the
> tracepoints, markers and LTTng features, to be used by userspace
> applications and libraries so they can add static instrumentation
> (as we currently do in the kernel). [...]
Just in case you're not aware, some API prior art for this is the
dtrace sdt.h widget (already supported by systemtap), and of course
it has no similarity to the various kernel tracing APIs.
- FChE
next prev parent reply other threads:[~2009-06-24 16:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4A412702.80707@polymtl.ca>
[not found] ` <20090623191128.GA19010@Krystal>
[not found] ` <20090623191513.GA20253@Krystal>
2009-06-24 0:43 ` Dual-licensing LTTng, marker and tracepoints under GPLv2+/LGPLv2.1+ Mathieu Desnoyers
2009-06-24 8:33 ` Ingo Molnar
2009-06-24 14:14 ` Mathieu Desnoyers
2009-06-24 16:33 ` Frank Ch. Eigler [this message]
2009-06-24 16:49 ` Mathieu Desnoyers
2009-06-24 17:23 ` Paul E. McKenney
2009-06-29 23:00 ` Mark Wielaard
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=y0mprctzj5v.fsf@fche.csb \
--to=fche@redhat.com \
--cc=bob@watson.ibm.com \
--cc=compudj@krystal.dyndns.org \
--cc=hch@infradead.org \
--cc=karim@opersys.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ltt-dev@lists.casi.polymtl.ca \
--cc=michel.dagenais@polymtl.ca \
--cc=mingo@elte.hu \
--cc=paulmck@linux.vnet.ibm.com \
--cc=pierre-marc.fournier@polymtl.ca \
--cc=rostedt@goodmis.org \
--cc=tzanussi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox