Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261510AbVBNSSs (ORCPT ); Mon, 14 Feb 2005 13:18:48 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261513AbVBNSSo (ORCPT ); Mon, 14 Feb 2005 13:18:44 -0500 Received: from rproxy.gmail.com ([64.233.170.202]:19978 "EHLO rproxy.gmail.com") by vger.kernel.org with ESMTP id S261510AbVBNSRg (ORCPT ); Mon, 14 Feb 2005 13:17:36 -0500 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=OTVgKpiD7Wq/wM2MTsoGMbjzhTEPGozGMFH8fYY490KKCoO06t/nsLdkNAV80BrIiPEl8e7yOee/6mGNejDaXfxBX2rsEZ6iZZezn97fAn2Wr2m8Ypo98VSSiKzQ5chY2uFFph41lTAWAx0nmDmME+Mo/1oKFzFN6I/EMVeIReA= Message-ID: <7579f7fb0502141017f5738d1@mail.gmail.com> Date: Mon, 14 Feb 2005 10:17:35 -0800 From: Matthew Jacob Reply-To: Matthew Jacob To: lm@bitmover.com, Jeff Sipek , Bartlomiej Zolnierkiewicz , linux-kernel@vger.kernel.org Subject: Re: [BK] upgrade will be needed In-Reply-To: <20050214154015.GA8075@bitmover.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <20050214020802.GA3047@bitmover.com> <58cb370e05021404081e53f458@mail.gmail.com> <20050214150820.GA21961@optonline.net> <20050214154015.GA8075@bitmover.com> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1141 Lines: 27 > So how would you suggest that we resolve it? The protection we need is > that people don't get to > > - use BK > - stop using BK so they can go work on another system > - start using BK again > - stop using BK so they can go work on another system > ... > I guess I don't see the advantage that accrues to BitMover Inc from this or what you're trying to do here. I'm not trying to add kerosene to a flame fest here, but I'm definitely scratching my head on this one. Is your concern that you don't want to provide a free tool to people who then turn around to compete with you? That is, you don't want BK to enable people to do things to harm BK and its ongoing development? I mean- you're certainly free to impose whatever license you want, and others are free to be happy or unhappy with that. I'm just trying to figure out what you're actually trying to accomplish here. - 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/