From: David Schwartz <davids@webmaster.com>
To: <Valdis.Kletnieks@vt.edu>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: Is the BitKeeper network protocol documented?
Date: Sun, 19 Jan 2003 17:05:02 -0800 [thread overview]
Message-ID: <20030120010504.AAA18836@shell.webmaster.com@whenever> (raw)
In-Reply-To: <200301200036.h0K0aCIJ012273@turing-police.cc.vt.edu>
On Sun, 19 Jan 2003 19:36:12 -0500, Valdis.Kletnieks@vt.edu wrote:
>Moral: Let's not get silly here...
Don't blame me. The GPL just says the "preferred" form and leaves us
to wonder. As I understand it, however, you cannot ship binaries of a
GPL'd project unless you can distribute the source code in the
"preferred form .. for making modifications to it".
I'm still perplexed what you do if the preferred modification form
for a work requires consent to a license more restrictive than the
GPL in order to make modifications to it. As I see it, you just can't
GPL such a project.
And you can't take a GPL'd work and turn it into a non-GPL'd work
and continue to distribute binaries.
DS
next prev parent reply other threads:[~2003-01-20 0:56 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030119235742.AAA13049%shell.webmaster.com@whenever>
2003-01-20 0:36 ` Is the BitKeeper network protocol documented? Valdis.Kletnieks
2003-01-20 1:05 ` David Schwartz [this message]
2003-01-20 14:28 ` Dana Lacoste
2003-01-20 19:00 ` David Schwartz
2003-01-20 19:31 ` David Lang
2003-01-20 20:19 ` David Schwartz
2003-01-20 20:40 ` John Bradford
2003-01-20 20:48 ` Andreas Dilger
2003-01-20 21:14 ` David Schwartz
2003-01-20 21:58 ` John Bradford
2003-01-20 21:37 ` Sam Ravnborg
2003-01-20 21:41 ` Rik van Riel
2003-01-21 16:04 ` Dana Lacoste
2003-01-21 18:34 ` David Schwartz
2003-01-21 18:49 ` John Bradford
2003-01-21 18:58 ` Sam Ravnborg
2003-01-21 19:27 ` Dana Lacoste
2003-01-21 21:04 ` David Schwartz
2003-01-21 19:51 ` Hua Zhong
2003-01-22 7:10 ` Jamie Lokier
2003-01-22 7:21 ` John Alvord
2003-01-22 15:18 ` Larry McVoy
2003-01-22 15:27 ` Dana Lacoste
2003-01-22 15:38 ` Larry McVoy
2003-01-20 1:46 ` David Lang
2003-01-20 1:52 ` Andre Hedrick
2003-01-21 19:22 Larry McVoy
-- strict thread matches above, loose matches on Subject: below --
2003-01-21 0:28 Cort Dougan
[not found] <20030120194430.AAA20700%shell.webmaster.com@whenever>
2003-01-20 20:32 ` Valdis.Kletnieks
2003-01-20 21:27 ` David Schwartz
2003-01-21 8:51 ` Horst von Brand
2003-01-20 15:55 Theodore Ts'o
2003-01-20 18:53 ` David Schwartz
[not found] <20030120010504.AAA18836%shell.webmaster.com@whenever>
2003-01-20 1:37 ` Valdis.Kletnieks
2003-01-18 6:22 Jamie Lokier
2003-01-18 4:33 Jamie Lokier
2003-01-18 4:57 ` David Schwartz
2003-01-18 5:10 ` Jamie Lokier
2003-01-18 7:23 ` David Schwartz
2003-01-18 5:02 ` Andrew Morton
2003-01-18 5:15 ` Jamie Lokier
2003-01-18 5:29 ` Larry McVoy
2003-01-18 6:11 ` Tupshin Harper
2003-01-18 6:20 ` Kevin Puetz
2003-01-18 6:39 ` Larry McVoy
2003-01-18 8:09 ` Jamie Lokier
2003-01-18 8:25 ` Andrew Morton
2003-01-18 14:22 ` Roman Zippel
2003-01-19 18:39 ` Andreas Dilger
2003-01-19 18:55 ` Jamie Lokier
2003-01-19 21:50 ` Roman Zippel
2003-01-19 23:26 ` Andreas Dilger
2003-01-19 23:57 ` David Schwartz
2003-01-20 0:20 ` Andreas Dilger
2003-01-20 0:38 ` David Schwartz
2003-01-20 15:52 ` Horst von Brand
2003-01-20 19:43 ` David Schwartz
2003-01-20 19:46 ` David Schwartz
2003-01-21 7:56 ` Horst von Brand
2003-01-20 14:18 ` Roman Zippel
2003-01-22 12:24 ` Matthias Andree
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=20030120010504.AAA18836@shell.webmaster.com@whenever \
--to=davids@webmaster.com \
--cc=Valdis.Kletnieks@vt.edu \
--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.