From: Andreas Dilger <adilger@clusterfs.com>
To: David Schwartz <davids@webmaster.com>
Cc: Roman Zippel <zippel@linux-m68k.org>,
Larry McVoy <lm@bitmover.com>,
linux-kernel@vger.kernel.org
Subject: Re: Is the BitKeeper network protocol documented?
Date: Sun, 19 Jan 2003 17:20:04 -0700 [thread overview]
Message-ID: <20030119172004.K1594@schatzie.adilger.int> (raw)
In-Reply-To: <20030119235742.AAA13049@shell.webmaster.com@whenever>; from davids@webmaster.com on Sun, Jan 19, 2003 at 03:57:40PM -0800
On Jan 19, 2003 15:57 -0800, David Schwartz wrote:
> On Sun, 19 Jan 2003 16:26:14 -0700, Andreas Dilger wrote:
> >There is nothing in the GPL which requires anyone to make their
> >changes available to you the minute they make them. The fact that
> >you have access to the changes within an hour of when they are made
> >far exceeds the requirements in the GPL, which only require that the
> >source code be made available if you distribute the OBJECT CODE OR
> >EXECUTABLE.
>
> I think you're ignoring the way the GPL defines the "source code".
> The GPL defines the "source code" as the preferred form for modifying
> the program. If the preferred form of a work for purposes of
> modifying it is live access to a BK repository, then that's the
> "source code" for GPL purposes.
I think you are ignoring the fact that this clause (#3) in the GPL only
relates only if "you copy or distribute the Program (or a work based on
it, under Section 2) in object code or executable form".
> >There are still lots of other ways to get the kernel source.
>
> You are using the conventional meaning of "source code", which is
> roughly, "whatever you compile to get the executable". However, this
> is not the "source" for GPL purposes. For GPL purposes, the source is
> the preferred form of a work for purposes of modifying it.
>
> This means you can't remove meta information that's useful for
> modifying because that is not the preferred form. Such meta
> information includes whatever is useful for modifying it, such as
> revision history and chain of custody.
>
> You can't have two "source"s, one a private repository that you
> prefer to use for making changes and the other an "obfuscated" public
> version you distribute for GPL compliance which is missing all the
> other useful information.
>
> Checking source out of a repository, separating away the revision
> history, is an obfuscatory act. The GPL prohibits such source
> obfuscation and requires you to distribute the source in whatever is
> the actual preferred form for modifying it. Really. Sorry.
Again you are ignoring the fact that there are other methods by which
the source code is available in the "preferred form", just not quite as
timely as directly from the BK repository (which is itself in a form, SCCS,
which does not require BK to access), and there is nothing in the GPL which
requires that the source be made avaible instantly.
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/
next prev parent reply other threads:[~2003-01-20 0:11 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
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 7:54 ` [OFFTOPIC] Is the repository of a GPL'd program itself under the GPL? Jamie Lokier
2003-01-20 0:50 ` Richard Stallman
2003-01-18 5:02 ` Is the BitKeeper network protocol documented? 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 [this message]
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
2003-01-18 6:22 Jamie Lokier
[not found] <20030119235742.AAA13049%shell.webmaster.com@whenever>
2003-01-20 0:36 ` Valdis.Kletnieks
2003-01-20 1:05 ` David Schwartz
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
[not found] <20030120010504.AAA18836%shell.webmaster.com@whenever>
2003-01-20 1:37 ` Valdis.Kletnieks
2003-01-20 15:55 Theodore Ts'o
2003-01-20 18:53 ` David Schwartz
[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-21 0:28 Cort Dougan
2003-01-21 19:22 Larry McVoy
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=20030119172004.K1594@schatzie.adilger.int \
--to=adilger@clusterfs.com \
--cc=davids@webmaster.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@bitmover.com \
--cc=zippel@linux-m68k.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
all inboxes | Powered by JetHome®