public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: anton@mips.complang.tuwien.ac.at (Anton Ertl)
To: Matthew Garrett <mgarrett@chiark.greenend.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Possible GPL Violation of Linux in Amstrad's E3 Videophone (me too???)
Date: Mon, 04 Oct 2004 09:42:54 GMT	[thread overview]
Message-ID: <2004Oct4.114254@mips.complang.tuwien.ac.at> (raw)
In-Reply-To: <2Lnl4-2w6-3@gated-at.bofh.it>

Matthew Garrett writes:
>The GPL requires that source be available to anyone who receives a copy
>of the binaries. There are three ways to do this, only two of which
>apply to commercial distribution. You can either:
>
>a) Provide the source alongside the binaries, or
>b) Provide a written offer (a text file on a CD is fine) for the source
>
>You never need to provide the source to anyone you don't provide the
>binaries to

If you go for option b, you have to provide the offer for the source
to _any third party_, so (in combination with option c) anyone could
take the offer and ask you for the source.

If you want to avoid having to keep track of the source code belonging
to a binary version, and keeping it around for three years, better
choose option a.

- anton
-- 
M. Anton Ertl                    Some things have to be seen to be believed
anton@mips.complang.tuwien.ac.at Most things have to be believed to be seen
http://www.complang.tuwien.ac.at/anton/home.html

       reply	other threads:[~2004-10-04  9:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2Lnl4-2w6-3@gated-at.bofh.it>
2004-10-04  9:42 ` Anton Ertl [this message]
2004-10-03 13:48 Possible GPL Violation of Linux in Amstrad's E3 Videophone (me too???) Gustavo Guillermo Perez
2004-10-03 22:23 ` Alan Cox
2004-10-03 22:39 ` Matthew Garrett
2004-10-05 18:41   ` Francois Romieu

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=2004Oct4.114254@mips.complang.tuwien.ac.at \
    --to=anton@mips.complang.tuwien.ac.at \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgarrett@chiark.greenend.org.uk \
    /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