From owner-freebsd-stable Tue Feb 24 19:06:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA13632 for freebsd-stable-outgoing; Tue, 24 Feb 1998 19:06:38 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA13602 for ; Tue, 24 Feb 1998 19:06:26 -0800 (PST) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id TAA19009; Tue, 24 Feb 1998 19:05:45 -0800 (PST) (envelope-from jdp) Message-Id: <199802250305.TAA19009@austin.polstra.com> To: john.saunders@scitec.com.au Subject: Re: stable branch funnies In-Reply-To: <34F25BC6.13E2F7A8@scitec.com.au> References: <34F25BC6.13E2F7A8@scitec.com.au> Organization: Polstra & Co., Seattle, WA Cc: stable@FreeBSD.ORG Date: Tue, 24 Feb 1998 19:05:45 -0800 From: John Polstra Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk In article <34F25BC6.13E2F7A8@scitec.com.au>, John Saunders wrote: > Then I read up on cvsup and [...] > Reading up on the cvsup man page [...] First let me say that it's heartwarming to find somebody who has read the man page. :-) > it says that it maintains a file(s) so it knows what versions it > has of each file. I have yet to locate these files and after 2 runs > of cvsup I would have expected these files to be created. Is these > missing files somehow confusing cvsup about what versions it has and > what it needs? As somebody already answered, they're in subdirectories of /usr/sup if you use the "/usr/share/examples/cvsup/stable-supfile" supfile. I'm sure they're being created, because cvsup would complain if it couldn't make the files. In short, everything's working the way it's supposed to. :-) -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message