From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10428 invoked by alias); 19 Dec 2003 20:23:22 -0000 Mailing-List: contact overseers-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: , Sender: overseers-owner@sources.redhat.com Received: (qmail 10381 invoked from network); 19 Dec 2003 20:23:21 -0000 Received: from unknown (HELO yosemite.airs.com) (209.128.65.135) by sources.redhat.com with SMTP; 19 Dec 2003 20:23:21 -0000 Received: (qmail 5376 invoked by uid 10); 19 Dec 2003 20:23:20 -0000 Received: (qmail 20388 invoked by uid 500); 19 Dec 2003 20:23:13 -0000 Mail-Followup-To: zack@codesourcery.com, jason-swarelist@molenda.com, per@bothner.com, overseers@sources.redhat.com, bkoz@redhat.com From: Ian Lance Taylor To: Benjamin Kosnik Cc: "Zack Weinberg" , jason-swarelist@molenda.com, per@bothner.com, overseers@sources.redhat.com Subject: Re: switch to subversion? References: <3FE35399.9090202@bothner.com> <20031219114252.A60180@molenda.com> <878yl8y4gc.fsf@egil.codesourcery.com> <20031219140858.7bdd8109.bkoz@redhat.com> Date: Fri, 19 Dec 2003 20:23:00 -0000 In-Reply-To: <20031219140858.7bdd8109.bkoz@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 X-SW-Source: 2003-q4/txt/msg00273.txt.bz2 Benjamin Kosnik writes: > >General agreement with this, also I don't think subversion scales to a > >project the size of gcc (much less /cvs/src!) yet, and I am currently > >thinking that monotone (http://www.venge.net/monotone/) will suit our > >purposes better. It isn't ready yet either, though. > > I would love to see gcc start testing monotone. I concurr: it's looking > very sharp. (It's also been tested with the gcc repository, which gives > me hope.) I would like to see a free version control system which implements change-sets. (My understanding is that Bitkeeper implements them.) In my mind, a change-set is essentially a large patch file (it would typically implement a particular feature). Applying a change set essentially means running patch. A version control system which supports change-sets makes it easy to create and to apply change-sets. It should do version tracking of change-sets, so that a single working tree can be the combination of several change-sets, and it should be possible to update a working tree to a new copy of a particular change-set. The application of change-sets is trickier than a three-way merge, because there is no known ancestor revision, so conflicts are hard to handle. But the concept is powerful. I wouldn't be very enthusiastic about switching to a new version control system if it didn't support change-sets. While I'm ready to believe that subversion and monotone are a better CVS, in my opinion CVS itself still works well enough for what it does. Ian