public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Manfred Spraul <manfred@colorfullife.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org
Subject: Re:  BK MetaData License Problem?
Date: Sun, 06 Oct 2002 14:40:16 +0200	[thread overview]
Message-ID: <3DA02F30.8040904@colorfullife.com> (raw)

>                              By transmitting the Metadata
>      to an Open Logging server, You hereby grant BitMover,
>      or any other operator of an Open Logging server, per-
>      mission  to  republish  the Metadata sent by the Bit-
>      Keeper Software to the Open Logging server.
> 

Where is the problem? This asks for a permission, not for exclusive rights.


> 	By transmitting the MetaData to an Open Logging server, You 
>         hereby also agree to license the MetaData under the same license
>         you license the data it describes.
> 
> (or something to that extent - i'm not a lawyer.)
> 

That's a problem for Linux, not for Larry.

If you send a patch to Linus this means you distribute a modification to 
GPLed source, which means it's automatically placed under the GPL.

What's missing is a comment in the BK-usage document that informs the 
submitter that he must give the permission to republish the commit info. 
i.e. asking Linus to pull from an url is not a private message to Linus, 
it's the equivalent of sending a mail to a public, moderated mailing list.

--
	Manfred


             reply	other threads:[~2002-10-06 12:34 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-06 12:40 Manfred Spraul [this message]
2002-10-06 13:13 ` BK MetaData License Problem? Ingo Molnar
2002-10-06 15:48   ` Marek Habersack
2002-10-06 16:26     ` Manfred Spraul
2002-10-06 19:11       ` Marek Habersack
2002-10-06 16:29   ` Alan Cox
2002-10-06 16:22     ` Larry McVoy
  -- strict thread matches above, loose matches on Subject: below --
2002-10-07  0:11 Hell.Surfers
2002-10-06 10:59 New BK " David S. Miller
2002-10-06 12:04 ` BK MetaData " Ingo Molnar
2002-10-06 11:52   ` David S. Miller
2002-10-06 12:18     ` jbradford
2002-10-06 12:35       ` jw schultz
2002-10-06 12:18     ` Ingo Molnar
2002-10-06 16:18     ` Daniel Berlin
2002-10-06 13:48   ` Russell King
2002-10-06 14:10     ` Ingo Molnar
2002-10-06 14:08       ` Russell King
2002-10-06 16:58         ` Alan Cox
2002-10-06 17:06           ` jbradford
2002-10-06 19:12           ` Marek Habersack
2002-10-06 14:23       ` jbradford
2002-10-06 19:39       ` Linus Torvalds
2002-10-06 20:00         ` Ingo Molnar
2002-10-06 22:52         ` Larry McVoy
2002-10-07  6:08           ` Ingo Molnar
2002-10-07  6:07             ` Larry McVoy
2002-10-06 17:17     ` Jes Sorensen
2002-10-06 17:38       ` Larry McVoy
2002-10-06 17:41       ` Alan Cox
2002-10-06 17:45         ` Jes Sorensen
2002-10-06 22:49           ` 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=3DA02F30.8040904@colorfullife.com \
    --to=manfred@colorfullife.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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