From: Rhys Ulerich <rhys.ulerich@gmail.com>
To: Brian Gough <bjg@network-theory.co.uk>
Cc: gsl-discuss@sourceware.org
Subject: Re: Licensing question
Date: Mon, 15 Jun 2009 14:53:00 -0000 [thread overview]
Message-ID: <4a00655d0906150753v269f1c2avd454f7565c480d5f@mail.gmail.com> (raw)
In-Reply-To: <m3prd54xus.wl%bjg@network-theory.co.uk>
> As I understand it, this wouldn't be needed - it is not necessary to
> make a separate release. Any code under the LGPL can always be used
> under the GPL by anyone, there are clauses in the LGPL which
> explicitly allow this.
Ahh... LGPL item 2b. Never saw that clause before.
> I'm assuming we are talking about version 3 of the GPL here...
Yes, this code is under LGPL version 3.
Thank you very much for the help,
Rhys
next prev parent reply other threads:[~2009-06-15 14:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-13 18:40 Rhys Ulerich
2009-06-15 10:30 ` Brian Gough
2009-06-15 14:53 ` Rhys Ulerich [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-06-06 9:26 Tom Browder
2000-06-08 11:59 ` Mark Galassi
2000-06-05 13:20 Herman Bruyninckx
2000-06-06 11:59 ` Brian Gough
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=4a00655d0906150753v269f1c2avd454f7565c480d5f@mail.gmail.com \
--to=rhys.ulerich@gmail.com \
--cc=bjg@network-theory.co.uk \
--cc=gsl-discuss@sourceware.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).