Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261618AbVBHSQu (ORCPT ); Tue, 8 Feb 2005 13:16:50 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261621AbVBHSQu (ORCPT ); Tue, 8 Feb 2005 13:16:50 -0500 Received: from ipcop.bitmover.com ([192.132.92.15]:38305 "EHLO mail.bitmover.com") by vger.kernel.org with ESMTP id S261618AbVBHSQg (ORCPT ); Tue, 8 Feb 2005 13:16:36 -0500 Date: Tue, 8 Feb 2005 10:16:34 -0800 To: Roman Zippel Cc: Stelian Pop , Francois Romieu , linux-kernel@vger.kernel.org Subject: Re: [RFC] Linux Kernel Subversion Howto Message-ID: <20050208181634.GA20261@bitmover.com> Mail-Followup-To: lm@bitmover.com, Roman Zippel , Stelian Pop , Francois Romieu , linux-kernel@vger.kernel.org References: <20050204183922.GC27707@bitmover.com> <20050204200507.GE5028@deep-space-9.dsnet> <20050204201157.GN27707@bitmover.com> <20050204214015.GF5028@deep-space-9.dsnet> <20050204233153.GA28731@electric-eye.fr.zoreil.com> <20050205193848.GH5028@deep-space-9.dsnet> <20050205233841.GA20875@bitmover.com> <20050208154343.GH3537@crusoe.alcove-fr> <20050208155845.GB14505@bitmover.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6+20040907i From: lm@bitmover.com (Larry McVoy) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1960 Lines: 41 On Tue, Feb 08, 2005 at 06:17:30PM +0100, Roman Zippel wrote: > Hi, > > On Tue, 8 Feb 2005, Larry McVoy wrote: > > > I think you are dreaming. You've gone from wanting enough information > > to supposedly debug your source tree to being explicit about wanting to > > recreate the entire BK history in a different system. The former is a > > reasonable request, I suppose, but the latter is just a blatent request > > for us to help debug and stress test a competing system. > > > > The answer is no, that's a clear violation of the license. > > You do realize what this practically means? It means exactly what it says, we're not going to help you work on a competing system. You are welcome to do that on your own, you are welcome to download all the patches you want from bkbits.net and figure out how to place them in your system, but we aren't going to help you any further than that, it doesn't make business sense for us to do so. We have to do things which make business sense because it is our business which provides you with the technology and the infrastructure you use. It costs money to do that, squeeze off the supply of money and the free ride goes away. I understand that you are unhappy with BK not being open source but unhappiness doesn't pay the bills. We are providing you with a great tool, good support, and excellent infrastructure. Not only do you not have a replacement for all of that you are actively trying to damage our business which provides you with all of that. That may force an open source answer but it would also do a lot of damage to the kernel development in the process. -- --- Larry McVoy lm at bitmover.com http://www.bitkeeper.com - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/