Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262908AbUJ0VXs (ORCPT ); Wed, 27 Oct 2004 17:23:48 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262729AbUJ0VXR (ORCPT ); Wed, 27 Oct 2004 17:23:17 -0400 Received: from DSL022.labridge.com ([206.117.136.22]:10764 "EHLO Perches.com") by vger.kernel.org with ESMTP id S262754AbUJ0VTO (ORCPT ); Wed, 27 Oct 2004 17:19:14 -0400 Subject: Re: BK kernel workflow From: Joe Perches To: Roman Zippel Cc: Larry McVoy , Linus Torvalds , Andrea Arcangeli , Paolo Ciarrocchi , Jeff Garzik , Linux Kernel , akpm@osdl.org In-Reply-To: References: <20041024233214.GA9772@work.bitmover.com> <20041025114641.GU14325@dualathlon.random> <1098707342.7355.44.camel@localhost.localdomain> <20041025133951.GW14325@dualathlon.random> <20041025162022.GA27979@work.bitmover.com> <20041025164732.GE14325@dualathlon.random> <20041026010141.GA15919@work.bitmover.com> <20041027035412.GA8493@work.bitmover.com> Content-Type: text/plain Date: Wed, 27 Oct 2004 14:16:15 -0700 Message-Id: <1098911775.8811.126.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1271 Lines: 32 On Wed, 2004-10-27 at 22:58 +0200, Roman Zippel wrote: > The complete development history of the Linux kernel is now effectly > locked into the bk format, you can get a summary of it, but that's it. > The data everyone put into a bk repository is now owned by BM and only if > you abide to the rules set by BM, do you have the permission to extract > some of the data again. You can completely forget the idea to one day > import "your" data into a different SCM system. Nonsense. I believe these statements to be wrong. I believe you might even know these statements are wrong. It's sad really. Subscribe to BK-KERNEL-COMMITS if you want to see every change ever made and track them. Use the web tools, use the CVS. Perhaps now you'll say something like because BK doesn't provide a cross-reference tool for every email to LK that proposes some patch that BK is stopping you from importing "your" data. Write your own import tools. Stop whining. Go write your own SCM. BitBucket anyone? Lots of activity on SF. - 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/