public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Filip Van Raemdonck <filipvr@xs4all.be>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: "any third party" (Re: Linksys WRT54G and the GPL)
Date: Wed, 11 Jun 2003 22:31:40 +0200	[thread overview]
Message-ID: <20030611203140.GD18726@debian> (raw)
In-Reply-To: <MDEHLPKNGKAHNMBLJOLKIEJKDJAA.davids@webmaster.com>

On Wed, Jun 11, 2003 at 01:12:59PM -0700, David Schwartz wrote:
> Adrian Bunk wrote:
> > On Wed, Jun 11, 2003 at 10:39:36AM -0700, Randolph Bentson wrote:
> > >
> > > If the distributor elects to distribute the object code or executable
> > > form under clause 3b, one might reasonably argue that the distributor
> > > need only distribute the source to those third parties in possession
> > > of the written offer which must be included.  Others may argue that
> > 
> > "Accompany it with a written offer, ..., to give any third party, ..., a
> > complete machine-readable copy of the corresponding source code..."
> >
> > This is non-ambiguous. You might _not_ "reasonably argue" about it, the
> > "any third party" leaves no room for other interpretations.
> 
> 	Think about this logically. Suppose a company releases a product and
> (maybe) accompanies it with such a written offer (I mean, how could you know
> for sure if you hadn't seen it?). You call the company up to try to enforce
> the offer. They say, "What offer?" You say, "the written offer that
> accompanied some copies of your product." You can't cite the text of the
> written offer, you can't specify any specific person they made the offer to.
<snip>
> Why specify a written offer if it just meant that you had to offer it?

Because:

http://www.gnu.org/licenses/gpl-faq.html#TOCWhatDoesWrittenOfferValid


Regards,

Filip

-- 
"Computers are not intelligent.  They only think they are."
	-- Martin Schulze

  reply	other threads:[~2003-06-11 20:18 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-08  2:41 Linksys WRT54G and the GPL Andrew Miklas
2003-06-08 11:54 ` Dave Jones
2003-06-08 14:23   ` Alan Cox
2003-06-08 18:13   ` uaca
2003-06-08 19:44 ` Colm MacCárthaigh
2003-06-08 20:14   ` Jörn Engel
2003-06-08 21:47   ` Russell King
2003-06-09 22:37   ` Daniel Phillips
2003-06-10 22:47     ` Andrew Miklas
2003-06-11 12:42       ` Alan Cox
2003-06-11 14:28       ` Kent Borg
2003-06-09  5:22 ` Frank Cusack
     [not found]   ` <20030609053010$504e@gated-at.bofh.it>
2003-06-09  8:28     ` Florian Weimer
2003-06-09 14:09   ` Horst von Brand
2003-06-09 18:23   ` Alan Cox
2003-06-09 21:33     ` Adrian Bunk
2003-06-09 21:50       ` David Schwartz
2003-06-09 22:21         ` Adrian Bunk
2003-06-10 20:17           ` Randolph Bentson
2003-06-11 15:38             ` Adrian Bunk
2003-06-11 17:39               ` Randolph Bentson
2003-06-11 19:22                 ` Adrian Bunk
2003-06-11 20:12                   ` David Schwartz
2003-06-11 20:31                     ` Filip Van Raemdonck [this message]
2003-06-11 20:51                       ` "any third party" (Re: Linksys WRT54G and the GPL) Eli Carter
2003-06-09  5:32 ` Linksys WRT54G and the GPL David Schwartz
2003-06-09  5:47   ` Frank Cusack
2003-06-09 16:53     ` David Schwartz
2003-06-09 18:25     ` Alan Cox
2003-06-09 21:37     ` Adrian Bunk

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=20030611203140.GD18726@debian \
    --to=filipvr@xs4all.be \
    --cc=linux-kernel@vger.kernel.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