Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sun, 16 Feb 2003 23:18:30 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sun, 16 Feb 2003 23:18:30 -0500 Received: from bjl1.jlokier.co.uk ([81.29.64.88]:21632 "EHLO bjl1.jlokier.co.uk") by vger.kernel.org with ESMTP id ; Sun, 16 Feb 2003 23:18:28 -0500 Date: Mon, 17 Feb 2003 04:31:08 +0000 From: Jamie Lokier To: Nicolas Pitre Cc: David Lang , Larry McVoy , Alan Cox , lkml Subject: Re: openbkweb-0.0 Message-ID: <20030217043108.GA16137@bjl1.jlokier.co.uk> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1355 Lines: 36 Nicolas Pitre wrote: > > CVS > > rsync > > FTP > > HTTP > > > > is there anything else people want? > > If you can manage to have a CVS repository that is always updated to the > minute with full history info etc. then this should be suficient to satisfy > all needs. Public CVS repositories are common enough so people should know > how to use them already. I expect most people would prefer read-only CVS for keeping up to date. However, rsync from the repository is generally _much_ faster than CVS if you are tracking changes, so I (an impatient modem user) prefer rsync. Also the SCCS repository is more fun for analysis and browsing programs than a CVS equivalent because some of the metadata would be lost converting to CVS. So I vote for rsync read-only access to the actual SCCS-ish repository files that BK manages. Ideally you'd ensure the tree offered through rsync was a consistent snapshot, offer a method of atomically updating the tree seen by rsync is a consistent snapshot. (Although this isn't crucial; BK's changeset files let you detect that at the client I believe). -- Jamie - 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/