All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Horst von Brand <brand@jupiter.cs.uni-dortmund.de>
Cc: Adrian Bunk <bunk@fs.tum.de>, linux-kernel@vger.kernel.org
Subject: Re: UnitedLinux violating GPL?
Date: Sat, 11 Jan 2003 19:27:59 +0000	[thread overview]
Message-ID: <10213.1042313279@passion.cambridge.redhat.com> (raw)
In-Reply-To: <200301111634.h0BGYGUt003680@eeyore.valparaiso.cl>


brand@jupiter.cs.uni-dortmund.de said:
>  Great! The "complete source code" for the kernel does include each
> and every single patch applied since linux-0.0.1? Guess I'll have to
> complain to a certain Torvalds then...

> Don't be silly. "Complete source code" means the source needed to
> rebuild the binary, nothing more. If that is a mangled version derived
> from some other  source, so be it. You are explicitly allowed to
> distribute changed versions, but only under GPL. [IANAL etc, so...]

I disagree. A preprocessed source file with all the variables renamed to 
random strings would suffice to rebuild the binary, and is obviously not 
acceptable -- being able to rebuild the binary is not the only criterion.

	"The source code for a work means the preferred form of the work
	for making modifications to it."

Note that the GPL doesn't say you have to give it in the preferred form for 
_building_ it, but the preferred form for _modifying_ it. 

In the opinion of many devlopers, the preferred form of the Linux kernel for
maintaining it is a set of individual patches against the closest
'official' release, and not a tarball containing already-modified code. 

--
dwmw2



  reply	other threads:[~2003-01-11 19:22 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
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 [this message]
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=10213.1042313279@passion.cambridge.redhat.com \
    --to=dwmw2@infradead.org \
    --cc=brand@jupiter.cs.uni-dortmund.de \
    --cc=bunk@fs.tum.de \
    --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 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.