Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263773AbTKRTjE (ORCPT ); Tue, 18 Nov 2003 14:39:04 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263774AbTKRTjE (ORCPT ); Tue, 18 Nov 2003 14:39:04 -0500 Received: from mail0-96.ewetel.de ([212.6.122.96]:21393 "EHLO mail0.ewetel.de") by vger.kernel.org with ESMTP id S263773AbTKRTjB (ORCPT ); Tue, 18 Nov 2003 14:39:01 -0500 To: Larry McVoy Cc: linux-kernel@vger.kernel.org Subject: Re: kernel.bkbits.net off the air In-Reply-To: References: Date: Tue, 18 Nov 2003 20:38:51 +0100 Message-Id: From: Pascal Schmidt X-CheckCompat: OK Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2125 Lines: 44 On Tue, 18 Nov 2003 19:50:18 +0100, you wrote in linux.kernel: > I'm curious as to why you would think this is better than the CVS gateway. Both things are tackling different issues. The CVS gateway means the data (code + checkin comments) is available in a free format. This means you as a company can do to BK's internal format whatever you want if you decide the old format is no longer up to it. The community still has all it wants in CVS format, as long as you continue the gateway service. A check-out and keep-up-to-date BK variant is a tool to access the latest version of a BK-using project (or any tagged version). This doesn't have to be the kernel obviously. It is still useful for kernel development - before sending in a patch to Linus' or Marcelo, people want to check out the latest BK tree to see if their patch applies cleanly. The CVS gateway, at least the data on kernel.org, lags behind the BK trees - for 2.4, the CVS repository at kernel.org still has "-pre9" in the Makefile although rc1 has been released already and the ChangeLog Marcelo posted indicated that he changed the Makefile in the BK repo. The lobotomized BK client would be useful for people who just want to get the latest code from some project, and nothing else. It means the project's maintainers wouldn't need to waste effort on creating .tgz snapshots (or similar); people could instead point to the BK repository and tell people who don't use closed-source tools on principle that they can use the loboBK ;) client to get the sources. As an aside, I personally rsync the CVS repository to be able to use "cvs diff" quickly (no fun having to contact a remote server on ISDN). I could use BK but it's not worth the effort for me to learn a new tool. So a checkout-only BK would not be useful to me, but I can see reasons why people would want one, outlined above. -- Ciao, Pascal - 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/