Return-Path: <John.Harrison-request@cl.cam.ac.uk>
Delivery-Date: 
Received: from leopard.cs.byu.edu (no rfc931) by swan.cl.cam.ac.uk 
          with SMTP (PP-6.5) outside ac.uk; Tue, 24 May 1994 13:56:37 +0100
Received: by leopard.cs.byu.edu (1.37.109.8/16.2) id AA02870;
          Tue, 24 May 1994 06:55:09 -0600
Sender: hol2000-request@lal.cs.byu.edu
Errors-To: hol2000-request@lal.cs.byu.edu
Precedence: bulk
Received: from concorde.inria.fr by leopard.cs.byu.edu 
          with SMTP (1.37.109.8/16.2) id AA02866;
          Tue, 24 May 1994 06:54:36 -0600
Received: from pauillac.inria.fr (pauillac.inria.fr [128.93.11.35]) 
          by concorde.inria.fr (8.6.9/8.6.9) with SMTP id OAA17800 
          for <hol2000@leopard.cs.byu.edu>; Tue, 24 May 1994 14:54:39 +0200
Received: from localhost.inria.fr by pauillac.inria.fr;
          Tue, 24 May 94 14:54:38 +0200
To: hol2000@leopard.cs.byu.edu
Subject: Re: RCS
In-Reply-To: Your message of Tue, 24 May 1994 14:46:25 +0200. <94May24.144631met_dst.8067@sunbroy14.informatik.tu-muenchen.de>
Date: Tue, 24 May 1994 14:54:38 +0200
Message-Id: <19026.769784078@pauillac.inria.fr>
From: Chet Murthy <Chet.Murthy@inria.fr>


We use CVS, as do a lot of sites which do heavy-duty source-code
development.

There isn't a way to check out code transparantly (unless you use NFS
to remote-mount the archive), but we regularly will check out a
source-code tree, RCP it to a remote site, say, from Paris to Lyon, or
Sophia-Antipolis, and after a month of work, will re-merge the code
back with the archive.

It takes around an hour (of human time) to do a re-merge.  Of course,
a human has to watch the thing, since it will try to guess merges and
stuff using rcsmerge.  But usually, it gets it right, and the human is
reduced to reading diff-outputs.

PCL-CVS is an emacs mode which makes it even more effortless.

I'd recommend it to anybody doing anything in the way of more than 10
files worth of source code.

--chet--