Date: Wed, 18 Mar 1998 22:24:03 -0600 (CST) From: Joel Ray Holveck <joelh@gnu.org> To: Matthew.Thyer@dsto.defence.gov.au Cc: 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: <199803190424.WAA08511@detlev.UUCP> In-Reply-To: <35108C62.DDFB1544@dsto.defence.gov.au> (message from Matthew Thyer on Thu, 19 Mar 1998 13:39:22 %2B1030) 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>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199803190424.WAA08511>