From: Larry McVoy <lm@bitmover.com>
To: Tupshin Harper <tupshin@tupshin.com>
Cc: Larry McVoy <lm@bitmover.com>, linux-kernel@vger.kernel.org
Subject: Re: RFC - tarball/patch server in BitKeeper
Date: Mon, 15 Dec 2003 08:02:46 -0800 [thread overview]
Message-ID: <20031215160246.GA3947@work.bitmover.com> (raw)
In-Reply-To: <3FDD4FB2.8020607@tupshin.com>
On Sun, Dec 14, 2003 at 10:07:46PM -0800, Tupshin Harper wrote:
> > Great, glad you understand that you are crossing the legal line.
>
> ??? what line am I crossing? Or do you mean that I would be if I were
> to do something, and if so, what is that something? I informed you the
> day that decided I was interested in exploring the internals of other
> SCM products, and deleted the bk binaries from my machine at the same
> time.
Tupshin, the BK license makes it clear that BK doesn't want to be reverse
engineered, we've been over this and over this. Furthermore, reverse
engineering for interoperability has a prerequisite that there is no other
way to get at the data and we give you tons of ways to get at the data.
You keep wanting more and more information about how BitKeeper manages
to do what it does and that certainly falls under reverse engineering.
Getting at the raw information is just another way to figure out how
BitKeeper manages that data, it's exactly the same as running a compiler
and looking at the assembly language it produces. You are annoyed that
we aren't giving you the data in the format you want with a roadmap that
says here is how we did it.
I wish you'd just drop it, this isn't the place to have this discussion,
every time we do anything to help the people who are actually doing kernel
development you or someone like you feels obligated to whine about BK one
more time because of your personal agenda which has nothing to do with
kernel development.
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
next prev parent reply other threads:[~2003-12-15 16:02 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-14 17:21 RFC - tarball/patch server in BitKeeper Larry McVoy
2003-12-14 23:05 ` Keith Owens
2003-12-14 23:44 ` Larry McVoy
2003-12-15 0:25 ` Keith Owens
2003-12-15 3:47 ` Larry McVoy
2003-12-14 23:17 ` Tupshin Harper
2003-12-14 23:43 ` Larry McVoy
2003-12-15 0:19 ` Tupshin Harper
2003-12-15 3:46 ` Larry McVoy
2003-12-15 6:07 ` Tupshin Harper
2003-12-15 16:02 ` Larry McVoy [this message]
2003-12-15 19:52 ` Tupshin Harper
2003-12-15 6:31 ` Martin J. Bligh
2003-12-15 12:11 ` Sergey Vlasov
2003-12-15 13:27 ` Ben Collins
2003-12-15 16:24 ` Sergey Vlasov
2003-12-15 16:32 ` Larry McVoy
2003-12-15 18:31 ` Andrea Arcangeli
2003-12-15 18:58 ` Larry McVoy
2003-12-15 19:40 ` Andrea Arcangeli
2003-12-15 21:44 ` Larry McVoy
2003-12-15 22:02 ` Andrea Arcangeli
2003-12-15 22:14 ` Larry McVoy
2003-12-15 22:44 ` Tupshin Harper
2003-12-15 23:13 ` Andrea Arcangeli
2003-12-15 22:36 ` Tupshin Harper
2003-12-15 22:46 ` Larry McVoy
2003-12-15 23:08 ` Tupshin Harper
2003-12-17 4:47 ` Matthew D. Pitts
2003-12-15 15:42 ` Larry McVoy
2003-12-15 15:55 ` Martin J. Bligh
2003-12-15 23:18 ` Chris Frey
2003-12-21 20:02 ` Pavel Machek
2003-12-21 20:46 ` John Bradford
2003-12-24 1: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=20031215160246.GA3947@work.bitmover.com \
--to=lm@bitmover.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tupshin@tupshin.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