From owner-freebsd-current Wed Mar 18 19:10:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA26598 for freebsd-current-outgoing; Wed, 18 Mar 1998 19:10:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA26502 for ; Wed, 18 Mar 1998 19:09:54 -0800 (PST) (envelope-from Matthew.Thyer@dsto.defence.gov.au) Received: from exchsa1.dsto.defence.gov.au (exchsa1.dsto.defence.gov.au [131.185.2.94]) by digger1.defence.gov.au (8.7.5/8.7.3) with ESMTP id NAA08896; Thu, 19 Mar 1998 13:38:06 +1030 (CST) Received: from fang.dsto.defence.gov.au ([131.185.2.5]) by exchsa1.dsto.defence.gov.au with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.1960.3) id H1923VTT; Thu, 19 Mar 1998 13:38:44 +0930 Received: from eddie.dsto.defence.gov.au (eddie.dsto.defence.gov.au [131.185.2.111]) by fang.dsto.defence.gov.au (8.8.5/8.8.5) with ESMTP id NAA19622; Thu, 19 Mar 1998 13:39:26 +1030 (CST) Received: from dsto.defence.gov.au (localhost [127.0.0.1]) by eddie.dsto.defence.gov.au (8.8.8/8.8.5) with ESMTP id NAA04755; Thu, 19 Mar 1998 13:39:26 +1030 (CST) Message-ID: <35108C62.DDFB1544@dsto.defence.gov.au> Date: Thu, 19 Mar 1998 13:39:22 +1030 From: Matthew Thyer Organization: Defence Science Technology Organisation X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: joelh@gnu.org CC: c5666305@comp.polyu.edu.hk, current@FreeBSD.ORG Subject: Using CVSUP and CTM together (Was Re: Disk munging problem with current solved) References: <199803171142.TAA07037@cssolar85.COMP.HKP.HK> <350E643D.A47CB903@camtech.net.au> <199803182240.QAA07391@detlev.UUCP> <35106C23.64774CD9@dsto.defence.gov.au> <199803190244.UAA08131@detlev.UUCP> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I dont know about this... hopefully someone else can comment on it. It would be good to be able to cvsup for a latest VM fix and then to be able to re-synchronize with CTM later. Also it would seem that CTM is not very useful for developers as they are required to update their tree before committing changes (in case what they were to change has been changed by others). Joel Ray Holveck wrote: > > >> I noticed that it is possible to cvsup a current ctm tree from > >> ctm.freebsd.org. I expect this to be either an alternative to using a > >> base delta (for instance, now that you'd have to ftp nearly 100 > >> deltas), or to allow you to resync a partially trashed source tree. > >> However, this is missing .ctm-status, which would seem to be fairly > >> important. > > Alas there is no synchronisation between CTM and cvs. > > Theoretically if you cvsupped at the same time as the person > > who makes the CTM deltas and you created the .ctm_status > > file yourself with the right number in it then you'd be right. > > However if you cvsup 1 minute later a couple of files somewhere > > in the tree may have been changed and then future CTM deltas > > would fail to apply. > > So no, you cannot use both CVS and CTM. > > It was my understanding that the ctm-src (or something like that) tag > from ctm.freebsd.org would fetch a CTM sync'd tree. > > -- > Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan > Fourth law of programming: > Anything that can go wrong wi > sendmail: segmentation violation - core dumped > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message