From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20182 invoked by alias); 11 Dec 2002 04:02:30 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 20173 invoked from network); 11 Dec 2002 04:02:29 -0000 Received: from unknown (HELO pizda.ninka.net) (216.101.162.242) by sources.redhat.com with SMTP; 11 Dec 2002 04:02:29 -0000 Received: from localhost (IDENT:davem@localhost.localdomain [127.0.0.1]) by pizda.ninka.net (8.9.3/8.9.3) with ESMTP id TAA03690; Tue, 10 Dec 2002 19:58:37 -0800 Date: Tue, 10 Dec 2002 23:07:00 -0000 Message-Id: <20021210.195836.117908392.davem@redhat.com> To: phil@jaj.com Cc: mark@mark.mielke.cc, zack@codesourcery.com, jsm28@cam.ac.uk, wlandry@ucsd.edu, gcc@gcc.gnu.org Subject: Re: source mgt. requirements solicitation From: "David S. Miller" In-Reply-To: <20021210225724.A22864@disaster.jaj.com> References: <20021211034224.GA20375@mark.mielke.cc> <20021210.194105.61848558.davem@redhat.com> <20021210225724.A22864@disaster.jaj.com> X-FalunGong: Information control. Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SW-Source: 2002-12/txt/msg00572.txt.bz2 From: Phil Edwards Date: Tue, 10 Dec 2002 22:57:24 -0500 > With Bitkeeper I have all the revision history in my cloned tree so > there is zero need for me to every go out onto the network to do work > until I want to share my changes with other people. This also > decreases the load on the machine with the "master" repository. So does the rsync-repo technique. That's not distributed source management, that's "I copy the entire master tree onto my computer." If you make modifications to your local rsync'd master tree, you can't transparently push those changes to other people unless you setup anoncvs on your computer and tell them "use this as your master repo instead of gcc.gnu.org to get my changes". That's bolted onto the side, not part of the design.