Date: Wed, 18 Mar 1998 21:50:49 -0600 From: Richard Wackerbarth <rkw@dataplex.net> To: Matthew Thyer <Matthew.Thyer@dsto.defence.gov.au> Cc: joelh@gnu.org, c5666305@comp.polyu.edu.hk, current@FreeBSD.ORG Subject: Re: Using CVSUP and CTM together (Was Re: Disk munging problem with current solved) Message-ID: <l03130308b13643d4b470@[208.2.87.4]> In-Reply-To: <35108C62.DDFB1544@dsto.defence.gov.au> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
At 9:09 PM -0600 3/18/98, Matthew Thyer wrote: >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. The ability to do this is somewhat limited by the problems associated in jumping from one CVSup server to another. You can use the CVSup server on ctm.freebsd.org in conjunction with CTM because it's source is the <cvs-cur> CTM distribution. However, that is not really a help if your intention is to try to beat the latency of CTM. CTM is delayed because (1) it is run only a few times each day, and (2) it does not have access to the master source. The CTM distributions themselves are generated from a copy of a copy of the master tree as it has no better access than to CVSup from one of the CVSup sites just the same as you would do. In fact, the deltas are often delayed because the CVSup update is rejected because those servers are too busy. >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). That would depend on the amount of latency that the developer can accept. If he knows that he is the only one working on a particular part of the tree, he is fairly safe in ingoring the pre-undate sync. CVS will "complain" if he gets caught in a race. If this happens, the update is rejected. The user must resync the affected file and try again. As long as such failures are very infrequent, it may not be a problem. Richard Wackerbarth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?l03130308b13643d4b470>