linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bryan Andersen <bryan@bogonomicon.net>
To: Zack Gilburd <zack@tehunlose.com>, linux-kernel@vger.kernel.org
Subject: Re: developers and GPL in products (Was: Re: GPL violations by wireless manufacturers)
Date: Tue, 24 Jun 2003 19:39:56 -0500	[thread overview]
Message-ID: <3EF8EF5C.4000005@bogonomicon.net> (raw)
In-Reply-To: 200306241727.51092.zack@tehunlose.com

Zack Gilburd wrote:
> Not exactly.  By my understanding of the GPL, if you plan on distributing 
> binaries outside of your corporation, you MUST make the source available to 
> any and all third parties.  In adition, you must bundle the source code with 
> the binary.

Please actually read the GPL License before you spew.

GPL only requires you to distribute source to those you distribute 
binaries to, not everybody.  If the binary seller wishes they can 
provide source to everybody but it is not required.

- Bryan




  reply	other threads:[~2003-06-25  0:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-24 10:10 GPL violations by wireless manufacturers vanstadentenbrink
2003-06-24 10:38 ` David Schwartz
2003-06-24 11:20   ` vanstadentenbrink
2003-06-24 18:18     ` David Schwartz
2003-06-24 23:37       ` vanstadentenbrink
2003-06-25  2:42       ` Horst von Brand
2003-06-29  3:14         ` Andre Hedrick
2003-06-24 18:25     ` developers and GPL in products (Was: Re: GPL violations by wireless manufacturers) Roger Larsson
2003-06-24 23:26       ` Krzysztof Halasa
2003-06-25  0:27       ` Zack Gilburd
2003-06-25  0:39         ` Bryan Andersen [this message]
2003-06-25  0:41         ` developers and GPL in products (Was: Re: GPL violations by wi reless manufacturers) David Lang
2003-06-25  0:47         ` developers and GPL in products (Was: Re: GPL violations by wireless manufacturers) Robins Tharakan
2003-06-25  3:21           ` Brian Davids

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=3EF8EF5C.4000005@bogonomicon.net \
    --to=bryan@bogonomicon.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zack@tehunlose.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 NNTP newsgroup(s).