From: Christian Fredrik Kalager Schaller <Uraeus@linuxrising.org>
To: linux-kernel@vger.kernel.org
Subject: Re: Permission to use atomic code under LGPL
Date: 31 Jan 2003 12:56:24 +0100 [thread overview]
Message-ID: <1044014183.1127.13.camel@thebox> (raw)
In-Reply-To: <1043776362.2939.14.camel@thebox>
Hi,
I got no objections to my request to use these few lines under the LGPL
so I will now update our sourcefile to make sure linus gets copyright
and origin is informed of. Thanks a lot guys!
Christian
On Tue, 2003-01-28 at 18:52, Christian Fredrik Kalager Schaller wrote:
> Hi,
> I am with the GStreamer project (www.gstreamer.net). We did a small
> license audit the other day and discovered we included some code from
> the kernel. GStreamer uses the LGPL so this is a problem for us.
>
> The code in question is the atomic code and is included in our
> sourcefile below. Do the person(s) in question responsible for this code
> mind if we re-license it under the LGPL?
>
> We will of course add comments in the code stating its origin with
> copyrights etc.
>
> I am not subscribed to the list so if anyone has objections to this
> relicensing of this particular piece of code, please CC me any
> responses.
>
> Sincerely,
> Christian
--
Christian Fredrik Kalager Schaller <Uraeus@linuxrising.org>
next prev parent reply other threads:[~2003-01-31 11:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-28 17:52 Permission to use atomic code under LGPL Christian Fredrik Kalager Schaller
2003-01-30 7:46 ` Pavel Machek
2003-01-31 11:56 ` Christian Fredrik Kalager Schaller [this message]
2003-01-31 12:01 ` Christoph Hellwig
2003-01-31 12:12 ` Christian Fredrik Kalager Schaller
2003-01-31 12:47 ` Mike A. Harris
2003-01-31 12:34 ` Russell King
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=1044014183.1127.13.camel@thebox \
--to=uraeus@linuxrising.org \
--cc=linux-kernel@vger.kernel.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.