public inbox for gsl-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Anton Fokin <anton.fokin@smartquant.com>
To: Brian Gough <bjg@network-theory.co.uk>
Cc: smartquant@yahoogroups.com, gsl-discuss@sourceware.cygnus.com
Subject: Re: [smartquant] Re: GPL license violation? [GNU Scientific Library]
Date: Sat, 10 Nov 2001 02:37:00 -0000	[thread overview]
Message-ID: <3BF3DA99.B884AEBF@smartquant.com> (raw)
Message-ID: <20011110023700.8kl_WaTrKN8eDL31NEg5eRhc_YfVqzvcRz58Ak2yhds@z> (raw)
In-Reply-To: <15347.55350.938075.320053@debian>

Kevin,

could you ask for a legal advise for us ? :)

Cheers,
Anton

Brian Gough wrote:

> Anton Fokin writes:
>  > Not exactly, see lines from GPL FAQ. Moreover, if I distribute libGSL under
>  > GPL (or whatever compatible license) together with R-Quant kernel which is
>  > not under GPL, would it solve your problem?
>
> I'll just have to refer you to my previous message and say it is your
> responsiblity to comply with the license of GSL when redistributing
> any related software --- you may want to take legal advice in case of
> any doubt.  Since your project is not free software I can't offer any
> specific advice apart from that.  The safest option is not to use GSL
> in non-free projects.
>
> regards,
> --
> Brian Gough
>
> ----------------------------------------------------------------------
> Network Theory Ltd            Phone: +44 (0)117 3179309
> 15 Royal Park                   WWW: http://www.network-theory.co.uk/
> Clifton                       Email: bjg@network-theory.co.uk
> Bristol BS8 3AL
> ----------------------------------------------------------------------

  parent reply	other threads:[~2001-11-15 15:13 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200111132351.PAA25299@eskimo.com>
     [not found] ` <3BF23743.AAEC520D@smartquant.com>
2001-12-19 13:20   ` Ferdinando Ametrano
2001-11-05  5:51     ` Ferdinando Ametrano
2001-12-19 13:20     ` Anton Fokin
2001-11-06  8:02       ` Anton Fokin
2001-12-19 13:20       ` Ferdinando Ametrano
2001-11-06  9:53         ` Ferdinando Ametrano
2001-12-19 13:20         ` Anton Fokin
2001-11-07 20:08           ` Anton Fokin
2001-12-19 13:20       ` Anton Fokin
2001-12-19 13:20       ` Brian Gough
2001-11-08  7:03         ` Brian Gough
2001-12-19 13:20         ` Brian Gough
2001-11-08  7:38           ` Brian Gough
2001-12-19 13:20           ` [smartquant] " Anton Fokin
2001-11-09  6:07             ` Anton Fokin
2001-12-19 13:20             ` Brian Gough
2001-11-09  9:19               ` Brian Gough
2001-12-19 13:20               ` Anton Fokin [this message]
2001-11-10  2:37                 ` Anton Fokin
2001-12-19 13:20       ` Kenneth Geisshirt
2001-11-08  2:15         ` Kenneth Geisshirt
2001-12-19 13:20         ` [smartquant] " Anton Fokin
2001-11-08  6:56           ` Anton Fokin
2001-12-19 13:20     ` Ferdinando Ametrano
2001-12-19 13:20 [smartquant] " Edwin Robert Tisdale
2001-11-14  3:33 ` Edwin Robert Tisdale
  -- strict thread matches above, loose matches on Subject: below --
2001-12-19 13:20 Edwin Robert Tisdale
2001-11-13  8:44 ` Edwin Robert Tisdale
2001-12-19 13:20 ` José Miguel Buenaposada
2001-11-13  9:24   ` José Miguel Buenaposada
2001-12-19 13:20   ` José Miguel Buenaposada
2001-12-19 13:20 ` Ferdinando Ametrano
2001-11-14  2:36   ` Ferdinando Ametrano
2001-12-19 13:20   ` Ferdinando Ametrano
2001-12-19 13:20 Edwin Robert Tisdale
2001-11-11  7:20 ` Edwin Robert Tisdale
2001-12-19 13:20 ` Brian Gough
2001-11-12  2:00   ` Brian Gough
2001-12-19 13:20 Edwin Robert Tisdale
2001-11-14  2:37 ` Edwin Robert Tisdale
2001-12-19 13:20 ` Ferdinando Ametrano
2001-11-14  3:04   ` Ferdinando Ametrano
2001-12-19 13:20   ` Dirk Eddelbuettel
2001-11-14  3:21     ` Dirk Eddelbuettel
2001-12-19 13:20     ` Dirk Eddelbuettel

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=3BF3DA99.B884AEBF@smartquant.com \
    --to=anton.fokin@smartquant.com \
    --cc=bjg@network-theory.co.uk \
    --cc=gsl-discuss@sourceware.cygnus.com \
    --cc=smartquant@yahoogroups.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).