mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@clusterfs.com>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: Larry McVoy <lm@bitmover.com>, linux-kernel@vger.kernel.org
Subject: Re: Is the BitKeeper network protocol documented?
Date: Sun, 19 Jan 2003 16:26:14 -0700	[thread overview]
Message-ID: <20030119162614.I1594@schatzie.adilger.int> (raw)
In-Reply-To: <3E2B1DA7.CAA76FFF@linux-m68k.org>; from zippel@linux-m68k.org on Sun, Jan 19, 2003 at 10:50:32PM +0100

On Jan 19, 2003  22:50 +0100, Roman Zippel wrote:
> Andreas Dilger wrote:
> > > IOW "You should be thankful for what I offer, if you don't like it, piss
> > > off!"  Might not be what you've intended, but that's what I arrived here
> > > and I'm sure I'm not the only one.
> > 
> > That's what he intended, and rightfully so.
> 
> I just wanted to make sure I understood correctly, I have an appropriate
> answer, but I can't word it as nicely as Larry.
> 
> >  You now have things you didn't
> > have before (i.e. hourly snapshots of Linus' tree) and you still aren't
> > happy.  I guess some people will never be happy with anything, so there is
> > no point in trying to appease them.
> 
> If you don't see the problem, maybe you should read
> /usr/src/linux/COPYING again for a change.

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.

If Linus uses BK to make pre-releases available to some people, that
does not appear to even invoke the "executable distribution" clause,
any more than him emailing patches to other developers privately.  If
Linus started making kernel patches available via a Lotus Notes database
(heaven forbid, I think even the IBM folks agree on that one ;-) doesn't
mean that IBM suddenly has to make all the details of Lotus Notes
available, or that Linus is forbidden to use tools as he wants.  There
are still lots of other ways to get the kernel source.

In fact (think about this for a while 8-o), EVERY SINGLE CHANGE that has
gone into the "official Linus kernel" had Linus doing the merge
(i.e. acting as editor of the combined work which is the kernel), which
may imply that Linus even owns a complete copyright over the entire
kernel source tree (i.e. compiled work).  Since he has never (or not
in the last decade, AFAIK) distributed a binary or object version of
the kernel, it may be that he isn't under any obligation to do anything
related to distribution under the GPL.  If you think that being the editor
of a combined work is not enough to give him copyright over the combined
work, then you need to learn your copyright law a bit more.  If it wasn't
for Linus acting as a "gatekeeper", the kernel would be full of the crap
that makes up 99% of the sourceforge projects out there.

Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/


  reply	other threads:[~2003-01-19 23:17 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 [this message]
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
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=20030119162614.I1594@schatzie.adilger.int \
    --to=adilger@clusterfs.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®