From owner-cvs-all Mon Dec 14 14:32:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA23494 for cvs-all-outgoing; Mon, 14 Dec 1998 14:32:54 -0800 (PST) (envelope-from owner-cvs-all@FreeBSD.ORG) Received: from server.amis.net (server.amis.net [195.10.52.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA23469; Mon, 14 Dec 1998 14:32:45 -0800 (PST) (envelope-from blaz@gold.amis.net) Received: (from uucp@localhost) by server.amis.net (8.8.8/8.8.8) with UUCP id XAA18750; Mon, 14 Dec 1998 23:32:07 +0100 (CET) Received: from localhost (blaz@localhost) by gold.amis.net (8.9.1/8.8.8) with ESMTP id XAA03405; Mon, 14 Dec 1998 23:26:51 +0100 (CET) Date: Mon, 14 Dec 1998 23:26:51 +0100 (CET) From: Blaz Zupan To: Dag-Erling Smorgrav cc: Mikael Karpberg , cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: src/etc Makefile In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk > 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 Are there really so many "flag" days? If we put the most recent events on top, a user can quite simply find out what he needs to do to make his "make world" work. > 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. It is simple: just take a look at the creation date of your binaries (like /bin/ls or something else you know you haven't recompiled separately). This tells you the date you last made world ;) Blaz Zupan, blaz@medinet.si, http://home.amis.net/blaz Medinet d.o.o., Linhartova 21, 2000 Maribor, Slovenia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message