public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Larry McVoy <lm@bitmover.com>
To: Jesse Pollard <jesse@cats-chateau.net>
Cc: Larry McVoy <lm@bitmover.com>,
	Leandro Guimar?es Faria Corsetti Dutra  <lgcdutra@terra.com.br>,
	linux-kernel@vger.kernel.org
Subject: Re: Switching to the OSL License, in a dual way.
Date: Fri, 25 Jul 2003 07:55:34 -0700	[thread overview]
Message-ID: <20030725145534.GB13840@work.bitmover.com> (raw)
In-Reply-To: <03072508173301.16381@tabby>

On Fri, Jul 25, 2003 at 08:17:33AM -0500, Jesse Pollard 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...

Oh, I see, you violate our license, your license is revoked, and
now you have the write to reverse engineer BK?  Show me the law which 
says that is true.

BK has a command that will take a BK tree and produce pure SCCS files,
there is even a GNU SCCS clone so tell me again you need to go poking
around in BK?

This whole thread is nuts.  First of all, there is no need to do so other
than to try and piss us off.  Second of all, it's completely unrealistic
to think you can reverse engineer it and keep up with our advancements.

> Even though the data is still ASCII, the interrelationships between the
> parts of the data is still "data". And extracting/viewing that would
> require the reverse enginnering.

And those relationships are available from the command line, using BK 
commands.  In other words, you're just trying to yank my chain.  Give
it a rest or join the rest of the wankers in my procmailrc.  Think about
that, one day you may need something from me and I'll never see your 
request, it will be languishing in /dev/null with the rest of wankers.
-- 
---
Larry McVoy              lm at bitmover.com          http://www.bitmover.com/lm

  reply	other threads:[~2003-07-25 14:40 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-24  8:40 Switching to the OSL License, in a dual way 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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2003-07-24 10:35 Samium Gromoff
2003-07-24 11:51 Dean McEwan
2003-07-24 22:25 ` Stefan Reinauer
2003-07-25  9:34 Samium Gromoff
2003-07-25 13:27 ` Gaël Le Mignot
2003-07-25 15:33 John Bradford
2003-07-25 15:36 ` Valdis.Kletnieks
2003-07-26 19:46 Hank Leininger
2003-07-26 20:20 John Bradford

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=20030725145534.GB13840@work.bitmover.com \
    --to=lm@bitmover.com \
    --cc=jesse@cats-chateau.net \
    --cc=lgcdutra@terra.com.br \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox