From: Larry McVoy <lm@bitmover.com>
To: Andrea Arcangeli <andrea@suse.de>
Cc: Larry McVoy <lm@bitmover.com>, linux-kernel@vger.kernel.org
Subject: Re: RFC - tarball/patch server in BitKeeper
Date: Mon, 15 Dec 2003 14:14:10 -0800 [thread overview]
Message-ID: <20031215221410.GC8130@work.bitmover.com> (raw)
In-Reply-To: <20031215220257.GM6730@dualathlon.random>
On Mon, Dec 15, 2003 at 11:02:57PM +0100, Andrea Arcangeli wrote:
> On Mon, Dec 15, 2003 at 01:44:52PM -0800, Larry McVoy wrote:
> > all. It's our tool and the use of our tool to export information how the
>
> is the web your tool too?
The web isn't a tool and it certainly isn't our tool. The web server on
bkbits.net is our tool, that's BitKeeper serving up the web pages directly.
> in your previous email you said the information is available via bkbits
> web. But in an older email you said if we would use the web to fetch
> information you would shut it down (for whatever reason, not relevant
> for this email). Please clarify this single point: is the "web" a tool
> we can use to fetch information?
I said I'd shut it down if you melted down the T1 line. We have dual
T1 lines and rate limited them on both ends so that problem is gone.
You can grab all the patches you want from bkbits.net until you start
using those patches to populate another SCM system because at that point
you are using BK in violation of the BK license.
Tupshin wants both the patches and all the details of how the patches have
been put together. I know why he wants it, it's a ton of useful test data
if what you are doing is building a clone of BitKeeper, and that's exactly
why he can't have all the information he wants. It's disingenuous of him
to pretend it is a freedom of speech issue, but I think it's obvious to
everyone what is going on here. If he was actually a kernel developer
using BK he'd be asking us to reduce the amount of information contained
in BitKeeper so that it ran faster which is what Linus wants us to do.
This is all about someone trying to circumvent our license, not about
some valuable information that BK is losing or hiding.
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
next prev parent reply other threads:[~2003-12-15 22:14 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
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 [this message]
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=20031215221410.GC8130@work.bitmover.com \
--to=lm@bitmover.com \
--cc=andrea@suse.de \
--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