Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261667AbTIYShY (ORCPT ); Thu, 25 Sep 2003 14:37:24 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261689AbTIYShY (ORCPT ); Thu, 25 Sep 2003 14:37:24 -0400 Received: from ebiederm.dsl.xmission.com ([166.70.28.69]:64595 "EHLO ebiederm.dsl.xmission.com") by vger.kernel.org with ESMTP id S261667AbTIYShT (ORCPT ); Thu, 25 Sep 2003 14:37:19 -0400 To: Dave Jones Cc: Linus Torvalds , andrea@kernel.org, Kernel Mailing List , Matthew Wilcox , Marcelo Tosatti , Larry McVoy Subject: Re: log-buf-len dynamic References: <20030925173648.GA19626@redhat.com> From: ebiederm@xmission.com (Eric W. Biederman) Date: 25 Sep 2003 12:35:42 -0600 In-Reply-To: <20030925173648.GA19626@redhat.com> Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 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: 1088 Lines: 19 Dave Jones writes: > 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. The linux infiniband project, is actually what I was thinking of. http://infiniband.sourceforge.net/ Eric - 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/