public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@fs.tum.de>
To: Philip Dodd <smpcomputing@free.fr>
Cc: Jeff Garzik <jgarzik@pobox.com>, linux-kernel@vger.kernel.org
Subject: Re: UnitedLinux violating GPL?
Date: Fri, 10 Jan 2003 01:27:05 +0100	[thread overview]
Message-ID: <20030110002705.GZ6626@fs.tum.de> (raw)
In-Reply-To: <3E1DFB8E.9050805@free.fr>

On Thu, Jan 09, 2003 at 11:45:34PM +0100, Philip Dodd wrote:

> With all due respect, I believe that the terms of the GPL only require 
> them to make it available to people who have the binaries, and only then 
> upon request.
>...

Why don't you _read_ the GPL instead of making wrong statements?

Section 3 clearly states that your "upon request" is wrong, the part 
that matches here is:

    b) Accompany it with a written offer, valid for at least three
    years, to give any third party, for a charge no more than your
    cost of physically performing source distribution, a complete
    machine-readable copy of the corresponding source code, to be
    distributed under the terms of Sections 1 and 2 above on a medium
    customarily used for software interchange; or,

 
> Cheers,
> 
> Philip

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2003-01-10  0:18 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-09 22:27 UnitedLinux violating GPL? Jeff Garzik
2003-01-09 22:45 ` Philip Dodd
2003-01-10  0:27   ` Adrian Bunk [this message]
2003-01-10  0:36     ` Cort Dougan
2003-01-10  2:40   ` John Jasen
2003-01-10  2:47     ` Jeff Garzik
2003-01-10 19:05       ` Samuel Flory
2003-01-09 22:53 ` Cort Dougan
2003-01-09 23:00 ` Tom Sightler
2003-01-09 23:06 ` GertJan Spoelman
2003-01-09 23:19 ` Lars Marowsky-Bree
2003-01-09 23:23   ` Jeff Garzik
2003-01-10 10:38     ` Pavel Machek
2003-01-17 20:12       ` Jeff Garzik
2003-01-09 23:45 ` Jeff V. Merkey
2003-01-09 22:46   ` Jeff Garzik
2003-01-10  1:22     ` Jeff V. Merkey
2003-01-10  0:31   ` Aaron T Porter
2003-01-10  8:34 ` Hubert Mantel
2003-01-10 10:46   ` Henning P. Schmiedehausen
2003-01-11 10:52     ` Christoph Hellwig
2003-01-10 10:55 ` Horst von Brand
2003-01-10 12:19   ` Adrian Bunk
2003-01-11 16:34     ` Horst von Brand
2003-01-11 19:27       ` David Woodhouse
2003-01-12 13:15         ` Hubert Mantel
2003-01-12 16:50           ` Alan Cox
2003-01-13 13:12             ` Dave Jones
2003-01-12 13:23         ` Horst von Brand
2003-01-11 10:50 ` Christoph Hellwig
2003-01-11 11:00   ` Andre Hedrick
2003-01-11 14:46   ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2003-01-10 12:25 Nicholas Berry
     [not found] <20030109224013$6e5e@gated-at.bofh.it>
     [not found] ` <20030111110011$3252@gated-at.bofh.it>
2003-01-11 11:51   ` Andi Kleen
2003-01-11 14:28     ` Christoph Hellwig
2003-01-11 14:44       ` Andi Kleen
2003-01-11 20:34 Protasevich, Natalie

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=20030110002705.GZ6626@fs.tum.de \
    --to=bunk@fs.tum.de \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=smpcomputing@free.fr \
    /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