From owner-freebsd-current Wed Feb 7 15:06:57 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA05475 for current-outgoing; Wed, 7 Feb 1996 15:06:57 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA05470 for ; Wed, 7 Feb 1996 15:06:56 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id QAA06706; Wed, 7 Feb 1996 16:04:01 -0700 From: Terry Lambert Message-Id: <199602072304.QAA06706@phaeton.artisoft.com> Subject: Re: CVS ISSUES To: julian@ref.tfs.com (Julian Elischer) Date: Wed, 7 Feb 1996 16:04:01 -0700 (MST) Cc: terry@lambert.org, current@FreeBSD.org In-Reply-To: <199602072155.NAA00382@ref.tfs.com> from "Julian Elischer" at Feb 7, 96 01:55:29 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org Precedence: bulk > Terry I think that what must have happend to you is a artifact > (no not an artisoft) of possibly having to install > everything piece-meal. > probably it was a boundary condition of getting started.. > what you suggest above is how I do ALL my development. > it hasn't gone wrong ONCE. Hopefully now that you are up and going > everything will work fine.. > > how about checking the following : > > wait for a commit message on the kernel. > go to your sys checked out tree, > make some change to the file that the commit was about. > sup the new CVS tree. (check the new change arrives) > do a cvs diff > check what is in the diff > do a cvs update > check the file got the new changes > do a cvs diff > check the contents again. > remove the file > cvs update it again to refetch the unmodified (by you) version I will try this diagnostic and let you know. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.