Return-Path: 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 14:08:09 +0100 Received: by leopard.cs.byu.edu (1.37.109.8/16.2) id AA02950; Tue, 24 May 1994 07:04:29 -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 AA02946; Tue, 24 May 1994 07:04:18 -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 PAA18131 for ; Tue, 24 May 1994 15:04:21 +0200 Received: from localhost.inria.fr by pauillac.inria.fr; Tue, 24 May 94 15:04:21 +0200 To: hol2000@leopard.cs.byu.edu Subject: Re: RCS In-Reply-To: Your message of Tue, 24 May 1994 14:54:38 +0200. <19026.769784078@pauillac.inria.fr> Date: Tue, 24 May 1994 15:04:20 +0200 Message-Id: <19638.769784660@pauillac.inria.fr> From: Chet Murthy >>>>> On Tue, 24 May 1994 14:54:38 +0200, Chet Murthy said: CM> There isn't a way to check out code transparantly (unless you CM> use NFS to remote-mount the archive), but we regularly will CM> check out a source-code tree, RCP it to a remote site, say, CM> from Paris to Lyon, or Sophia-Antipolis, and after a month of CM> work, will re-merge the code back with the archive. However, there is a package called "rCVS" from SLAC (Stanford) which does transparent remote CVS. I'm not too keen on their method, though, which is to transport the archive to the remote site, do the checkin, and transport back. I'd prefer if it transported the users' files to the archive-site. In addition, there is a comprehensive utility called CAVEMAN from LBL which automates a lot of CVS's idiosyncracies - they use it to manage lots of numerical code written by physicists and such. --chet--