Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 3 Mar 2003 21:19:19 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 3 Mar 2003 21:19:19 -0500 Received: from e31.co.us.ibm.com ([32.97.110.129]:62612 "EHLO e31.co.us.ibm.com") by vger.kernel.org with ESMTP id ; Mon, 3 Mar 2003 21:19:18 -0500 Date: Mon, 03 Mar 2003 18:20:03 -0800 From: "Martin J. Bligh" To: David Lang , Andrea Arcangeli cc: Larry McVoy , Jeff Garzik , Alan Cox , Arador , "Adam J. Richter" , Linux Kernel Mailing List , pavel@janik.cz, pavel@ucw.cz Subject: Re: BitBucket: GPL-ed *notrademarkhere* clone Message-ID: <592860000.1046744403@flay> In-Reply-To: References: X-Mailer: Mulberry/2.1.2 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 800 Lines: 21 >> Just curious, this also means that at least around the 80% of merges >> in Linus's tree is submitted via a bitkeeper pull, right? >> >> Andrea > > remember how Linus works, all normal patches get copied into a single > large patch file as he reads his mail then he runs patch to apply them to > the tree. I think this would make the entire batch of messages look like > one cset. I think he also creates subtrees, applies flat patches to those, then merges the subtrees back into his main tree as a bk-merge ... won't that distort the stats? M. - 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/