From owner-cvs-all Mon Dec 14 04:38:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA19094 for cvs-all-outgoing; Mon, 14 Dec 1998 04:38:34 -0800 (PST) (envelope-from owner-cvs-all@FreeBSD.ORG) Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA18992; Mon, 14 Dec 1998 04:38:26 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.1/8.9.1) id NAA62624; Mon, 14 Dec 1998 13:38:01 +0100 (CET) (envelope-from des) To: Blaz Zupan Cc: Mikael Karpberg , cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: src/etc Makefile References: From: Dag-Erling Smorgrav Date: 14 Dec 1998 13:37:59 +0100 In-Reply-To: Blaz Zupan's message of "Sun, 13 Dec 1998 22:45:24 +0100 (CET)" Message-ID: Lines: 17 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk Blaz Zupan writes: > Ok, I can go and browse through the mailing list archives for any HEADS-UP > messages and hope that I find all the important changes. But wouldn't it > be much easier to just read some text file, which has a checklist of > things to do, like: > > - check that user "foo" exists, if not create it > - make sure you have file /etc/bar.conf Such a file would need to be updated for *every* flag day, and would quickly grow large. And you'd have no end of trouble trying to find out where to start, because you might not remember the exact date of your last 'make world'. It's a nice idea, but it's impractical. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message