Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262722AbUJ1Cl3 (ORCPT ); Wed, 27 Oct 2004 22:41:29 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262725AbUJ1Cl3 (ORCPT ); Wed, 27 Oct 2004 22:41:29 -0400 Received: from fw.osdl.org ([65.172.181.6]:45242 "EHLO mail.osdl.org") by vger.kernel.org with ESMTP id S262722AbUJ1ClV (ORCPT ); Wed, 27 Oct 2004 22:41:21 -0400 Date: Wed, 27 Oct 2004 19:35:41 -0700 (PDT) From: Linus Torvalds To: Roman Zippel cc: Larry McVoy , Andrea Arcangeli , Joe Perches , Paolo Ciarrocchi , Jeff Garzik , Linux Kernel , akpm@osdl.org Subject: Re: BK kernel workflow In-Reply-To: Message-ID: References: <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> <20041028005412.GA8065@work.bitmover.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 885 Lines: 24 On Thu, 28 Oct 2004, Roman Zippel wrote: > > Actually the Commit numbers are far more interesting and here you have > difference of 56% you haven't explained. It's because CVS cannot handle what BK does. So when you do a BK merge, there's no way in hell that will be a CVS merge, and instead it ends up being one big commit of the branch. Merges happen pretty often, so these "big commits" aren't _that_ big (certainly nowhere near as big as a CVS banch merge tends to be - if only simply because nobody uses CVS for "small branches", the pain isn't worth it). Face it. BK is just better than CVS. It's not a 1:1 mapping. Linus - 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/