From owner-freebsd-current Wed Dec 30 22:19:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA26795 for freebsd-current-outgoing; Wed, 30 Dec 1998 22:19:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp4.nwnexus.com (smtp4.nwnexus.com [206.63.63.52]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA26790 for ; Wed, 30 Dec 1998 22:19:08 -0800 (PST) (envelope-from wrsomsky@halcyon.com) Received: from gramarye (evt-lx101-ip44.nwnexus.net [204.57.235.94]) by smtp4.nwnexus.com (8.8.8/8.8.8) with ESMTP id WAA30988; Wed, 30 Dec 1998 22:18:41 -0800 (PST) Received: (from wrsomsky@localhost) by gramarye (8.9.1/8.8.8) id SAA00388; Sun, 20 Dec 1998 18:53:39 -0800 (PST) (envelope-from wrsomsky) Message-ID: <19981220185338.A363@halcyon.com> Date: Sun, 20 Dec 1998 18:53:38 -0800 From: "William R. Somsky" To: John Polstra , nwestfal@Vorlon.odc.net Cc: current@FreeBSD.ORG Subject: Re: syncing 3.0-src tree with current References: <199812170539.VAA21583@vashon.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199812170539.VAA21583@vashon.polstra.com>; from John Polstra on Wed, Dec 16, 1998 at 09:39:36PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In article , > Neal Westfall wrote: > > > Is there an easy way to get a 3.0 source tree up to current? I will be > > doing this with CTM. Can I start with my 3.0 source tree or do I need > > to wipe it out and start clean with the fat delta? I didn't see any > > info on how to do this without starting from an empty src dir. Can > > this be done? On Wed, Dec 16, 1998 at 09:39:36PM -0800, John Polstra replied: > > I'll let others answer about CTM. But you can do it with CVSup. The > technique is described in the CVSup FAQ, at: > > http://www.polstra.com/projects/freeware/CVSup/ I'll follow up with this comment: It's mentioned in the handbook that you may want to use CTM instead of CVSup if you're running dialup, but I've found that in practice, CVSup works quite well over a dialup line. I was running CVSup happily w/ a 28.8K modem for quite a while. Now, the first time you run, esp if you have a far-divergent, or even empty /usr/src, it may take several hours, but once you're in sync, it only takes approx 5-15 minutes each time if you update once a week or so. CVSup is also nice in that it will easily handle arbitrary file deletions/changes/manglations of your /usr/src, whereas CTM, I believe, gets out of sync if something like that happens. The one thing I wish CVSup had was a way for it to tell you when there are _extra_ files in /usr/src (or whatever it's syncing) that it's not touching. CVSup will, as I understand it, delete a file if it's got a record that it's the one that created it, but if you add an arbitrary file, it gets completely ignored by CVSup. However, I've written a perl script to list for me any files in the /usr/src tree that list any such files for me. (It's be nice if cvsup itself had an option for this built in though). ________________________________________________________________________ William R. Somsky wrsomsky@halcyon.com Physicist, Baritone, Guitarist http://www.halcyon.com/wrsomsky To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message