public inbox for gsl-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Rhys Ulerich <rhys.ulerich@gmail.com>
To: gsl-discuss@sourceware.org
Subject: Licensing question
Date: Sat, 13 Jun 2009 18:40:00 -0000	[thread overview]
Message-ID: <4a00655d0906131139y1bd3a168x36fc1d113d73d870@mail.gmail.com> (raw)

Hi all,

I've got a licensing question.  An individual has some nice routines
that I believe fill gaps in the GSL integration functionality.  These
routines are LGPL.  Is it possible for the individual to make a
GPL/LGPL one-off release that could be pulled into GSL without
"screwing up" the LGPL licensing he currently uses?  Specifically,
could he continue to update and release his own routine modifications
under only the LGPL?

- Rhys

             reply	other threads:[~2009-06-13 18:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-13 18:40 Rhys Ulerich [this message]
2009-06-15 10:30 ` Brian Gough
2009-06-15 14:53   ` Rhys Ulerich
  -- 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=4a00655d0906131139y1bd3a168x36fc1d113d73d870@mail.gmail.com \
    --to=rhys.ulerich@gmail.com \
    --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).