From owner-freebsd-current Wed Mar 18 20:26:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA10231 for freebsd-current-outgoing; Wed, 18 Mar 1998 20:26:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wcc.wcc.net (wcc.wcc.net [208.6.232.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA10224 for ; Wed, 18 Mar 1998 20:26:08 -0800 (PST) (envelope-from piquan@wcc.wcc.net) Received: from detlev.UUCP (tnt135.wcc.net [208.10.139.135]) by wcc.wcc.net (8.8.8/8.8.8) with ESMTP id WAA23434; Wed, 18 Mar 1998 22:21:58 -0600 (CST) Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id WAA08511; Wed, 18 Mar 1998 22:24:03 -0600 (CST) (envelope-from joelh) Date: Wed, 18 Mar 1998 22:24:03 -0600 (CST) Message-Id: <199803190424.WAA08511@detlev.UUCP> To: Matthew.Thyer@dsto.defence.gov.au CC: c5666305@comp.polyu.edu.hk, current@FreeBSD.ORG In-reply-to: <35108C62.DDFB1544@dsto.defence.gov.au> (message from Matthew Thyer on Thu, 19 Mar 1998 13:39:22 +1030) Subject: Re: Using CVSUP and CTM together (Was Re: Disk munging problem with current solved) From: Joel Ray Holveck Reply-to: joelh@gnu.org 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> <35108C62.DDFB1544@dsto.defence.gov.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 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 machine I run -current on can afford to sit out a few hours while I wait for changes to hit CTM. (I'm used to waiting for a change to hit the net, what's the difference?) (And that's NOT meant as an insult to the kernel hackers!) > 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). I prefer to look at code that's not changing. Since most of the fast-paced changes are in the kernel, and I barely understand kernel code, then I'm okay. In other words, I'm relaxed about lag. Living in Texas, I have to be. Happy hacking, joelh -- 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