Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261707AbTIYRj5 (ORCPT ); Thu, 25 Sep 2003 13:39:57 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261695AbTIYRi1 (ORCPT ); Thu, 25 Sep 2003 13:38:27 -0400 Received: from pix-525-pool.redhat.com ([66.187.233.200]:36149 "EHLO lacrosse.corp.redhat.com") by vger.kernel.org with ESMTP id S261685AbTIYRhq (ORCPT ); Thu, 25 Sep 2003 13:37:46 -0400 Date: Thu, 25 Sep 2003 18:36:48 +0100 From: Dave Jones To: "Eric W. Biederman" Cc: Linus Torvalds , andrea@kernel.org, Kernel Mailing List , Matthew Wilcox , Marcelo Tosatti , Larry McVoy Subject: Re: log-buf-len dynamic Message-ID: <20030925173648.GA19626@redhat.com> Mail-Followup-To: Dave Jones , "Eric W. Biederman" , Linus Torvalds , andrea@kernel.org, Kernel Mailing List , Matthew Wilcox , Marcelo Tosatti , Larry McVoy References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.4i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 975 Lines: 22 On Thu, Sep 25, 2003 at 11:15:33AM -0600, Eric W. Biederman wrote: > And for the core kernel development this is true. There are subprojects > that are currently using BK that you can't even get the code without > BK. And the only reason they are using BK is they are attempting to > following how Linux is managed. So having the Linux kernel > development use BK does have some down sides. I was expecting this to come up when Linus first made sparse publically available only by bitkeeper, so I started the nightly snapshots. If there's any other Linux related project that's bitkeeper only let me know, and I'll be happy to host nightly snapshots of that too. Dave -- Dave Jones http://www.codemonkey.org.uk - 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/