From owner-freebsd-doc Mon Nov 8 12:21:42 1999 Delivered-To: freebsd-doc@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 8E4E114A17; Mon, 8 Nov 1999 12:21:41 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 7D7CE1CD623 for ; Mon, 8 Nov 1999 12:21:41 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Mon, 8 Nov 1999 12:21:41 -0800 (PST) From: Kris Kennaway To: doc@freebsd.org Subject: Outdated version information Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hmm, every time I happen to look at the FAQ/handbook/website to locate information for someone I seem to find another case of an outdated FreeBSD version being referred to as current (this time: http://www.freebsd.org/FAQ/preface.html#AEN53). We really need a system whereby these will be flagged and/or updated automatically each time a new release comes around. Perhaps by tagging sections related to a particular release and then "aging" them somehow, or presenting them on a list of "things to be checked that they're still current" - I don't know enough about the specifics of the build mechanism to suggest an explicit solution, but I'm sure one of you guys do. Any ideas? Kris ---- Cthulhu for President! For when you're tired of choosing the _lesser_ of two evils.. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message