From: Daniel Phillips <phillips@bonn-fries.net>
To: Larry McVoy <lm@bitmover.com>, linux-kernel@vger.kernel.org
Subject: Re: [OFF TOPIC] BK license change
Date: Sun, 21 Apr 2002 14:12:16 +0200 [thread overview]
Message-ID: <E16zGCW-0001EM-00@starship> (raw)
In-Reply-To: <20020421095715.A10525@work.bitmover.com>
On Sunday 21 April 2002 18:57, Larry McVoy wrote:
> I'm considering a change to the BKL which says that N days after a
> changeset is made, that changeset (and its ancestory) must be available
> on a public bk server. In other words, put a hard limit on how long
> you may hide.
More red tape is usually bad. You want to do it to protect your commericial
interests? Fine. However, the GPL does not need Bitkeeper to be its robocop.
GPL violations have a way of coming to light without this sort of automated
enforcement.
--
Daniel
next prev parent reply other threads:[~2002-04-22 12:11 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-21 16:57 [OFF TOPIC] BK license change Larry McVoy
2002-04-21 12:12 ` Daniel Phillips [this message]
2002-04-21 16:29 ` Greg KH
2002-04-22 7:33 ` Simon Fowler
2002-04-22 21:35 ` Larry McVoy
2002-04-21 22:14 ` Daniel Phillips
2002-04-22 22:29 ` Andreas Dilger
2002-04-21 22:52 ` Daniel Phillips
2002-04-22 23:12 ` Doug Ledford
2002-04-21 23:34 ` Daniel Phillips
2002-04-22 22:22 ` Jeff Garzik
2002-04-22 22:52 ` Larry McVoy
2002-04-25 15:01 ` Pavel Machek
2002-04-27 9:30 ` Florian Weimer
2002-04-27 13:45 ` Mr. James W. Laferriere
2002-04-27 20:34 ` Larry McVoy
2002-04-26 4:22 ` Pavel Machek
2002-04-29 19:34 ` Rik van Riel
2002-04-29 19:45 ` Larry McVoy
2002-04-30 5:36 ` Pavel Janík
-- strict thread matches above, loose matches on Subject: below --
2002-04-27 18:13 Christoph Lameter
2002-04-27 18:25 ` Russell King
2002-04-27 18:30 ` Alexander Viro
2002-04-27 21:50 ` Martin Dalecki
2002-04-28 16:55 ` Richard Gooch
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=E16zGCW-0001EM-00@starship \
--to=phillips@bonn-fries.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@bitmover.com \
/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