All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hank Leininger <linux-kernel@progressive-comp.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Switching to the OSL License, in a dual way.
Date: Sat, 26 Jul 2003 15:46:09 -0400	[thread overview]
Message-ID: <200307261946.h6QJk9GC002882@marc2.theaimsgroup.com> (raw)

On 2003-07-25, Jesse Pollard <jesse () cats-chateau ! net> wrote:

> On Thursday 24 July 2003 16:57, Larry McVoy wrote:
> [snip]
> > 
> > In other words, reverse engineering is ok if the product doesn't
> > provide access to your data, we do that already, poof, no reverse
> > engineering allowed.  So it's illegal to reverse engineer BK.

> Nonesense. If the business no longer has the licence to use BK (for
> whatever reason) then it no longer has access to the data. Now to
> get access to the data you must reverse engineer BK...

Or, just ask.  Larry has always been (or given the appearance of being)
open to handling special cases/requests reasonably[1].  Seriously, do you
think BM would turn down a "Er, we didn't see this coming, is it OK for us
to use our free-licensed BK one more time to export to SCCS or whatever? 
We promise there won't be a guy from the SCM team shoulder-surfing or
tcpdumping while we do so" request?  If they *did* turn down a reasonable
request, *then* maybe there would be something legitemate to flame them
about.

[1] Of course, the definition of "reasonable" will now be debated to death.

--
Hank Leininger <hlein@progressive-comp.com> 
  

             reply	other threads:[~2003-07-26 19:30 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-26 19:46 Hank Leininger [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-07-26 20:20 Switching to the OSL License, in a dual way John Bradford
2003-07-25 15:33 John Bradford
2003-07-25 15:36 ` Valdis.Kletnieks
2003-07-25  9:34 Samium Gromoff
2003-07-25 13:27 ` Gaël Le Mignot
2003-07-24 11:51 Dean McEwan
2003-07-24 22:25 ` Stefan Reinauer
2003-07-24 10:35 Samium Gromoff
2003-07-24  8:40 Dean McEwan
2003-07-24  8:58 ` Miles Bader
2003-07-24  9:46   ` Andre Hedrick
2003-07-24 18:06     ` Leandro Guimarães Faria Corsetti Dutra
2003-07-24 20:02       ` Andre Hedrick
2003-07-24 21:05         ` Leandro Guimarães Faria Corsetti Dutra
2003-07-24 21:57           ` Larry McVoy
2003-07-24 22:24             ` Leandro Guimarães Faria Corsetti Dutra
2003-07-25  9:56             ` Gaël Le Mignot
2003-07-25 14:39               ` Larry McVoy
2003-07-26  2:52                 ` Matthias Andree
2003-07-26  3:18                   ` Larry McVoy
2003-07-25 13:17             ` Jesse Pollard
2003-07-25 14:55               ` Larry McVoy
2003-07-25 15:15                 ` Gaël Le Mignot
2003-07-25 15:33                   ` Richard B. Johnson
2003-07-26 19:10             ` Rik van Riel
2003-07-26 19:23               ` Larry McVoy
2003-07-26 19:46                 ` Leandro Guimarães Faria Corsetti Dutra
2003-07-26 20:01                   ` Larry McVoy
2003-07-26 21:08                     ` Mr. James W. Laferriere
2003-07-26 20:21                 ` Bernd Eckenfels
2003-07-24  9:05 ` Leandro Guimarães Faria Corsetti Dutra
2003-07-27  9:21   ` Kai Henningsen
2003-07-24 11:30 ` viro

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=200307261946.h6QJk9GC002882@marc2.theaimsgroup.com \
    --to=linux-kernel@progressive-comp.com \
    --cc=hlein@progressive-comp.com \
    --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.