All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Friesen <cfriesen@nortel.com>
To: Charles Cazabon <linux@discworld.dyndns.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: GPL violation by CorAccess?
Date: Tue, 19 Apr 2005 12:59:09 -0600	[thread overview]
Message-ID: <426554FD.9010601@nortel.com> (raw)
In-Reply-To: <20050419183219.GB5670@discworld.dyndns.org>

Charles Cazabon wrote:
> Lennart Sorensen <lsorense@csclub.uwaterloo.ca> wrote:
> 
>>Well what is the case if you use unmodified GPL code, do you still have
>>to provide sources to the end user if you give them binaries? 
> 
> 
> Yes, or a written offer to provide sources, plus a copy of the GPL.  It's all
> spelled out pretty clearly in the GPL itself.

Or a nonprofit organization can simply point to the original 
source...but that doesn't apply in this case.

Chris

  reply	other threads:[~2005-04-19 19:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-19 17:57 GPL violation by CorAccess? Karel Kulhavy
2005-04-19 18:25 ` Lennart Sorensen
2005-04-19 18:32   ` Charles Cazabon
2005-04-19 18:59     ` Chris Friesen [this message]
2005-04-19 19:19   ` Richard B. Johnson
2005-04-19 19:59     ` Chris Friesen
2005-04-19 21:44       ` Richard B. Johnson
2005-04-19 23:37         ` Chris Friesen
2005-04-20  0:26           ` Richard B. Johnson
2005-04-20  7:30           ` Bernd Petrovitsch
2005-04-20 12:49             ` Steven Rostedt
2005-04-20 12:57               ` Arjan van de Ven
2005-04-20 13:07                 ` Steven Rostedt
2005-04-20 13:36                   ` Michael Poole
2005-04-20 13:37                   ` Arjan van de Ven
2005-04-20 17:18   ` Pavel Machek

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=426554FD.9010601@nortel.com \
    --to=cfriesen@nortel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@discworld.dyndns.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.