Date: Tue, 21 Jan 2003 20:18:02 +0100 From: Udo Erdelhoff <ue@nathan.ruhr.de> To: freebsd-doc@FreeBSD.ORG Subject: Re: Adding a publication date to the installation instructions Message-ID: <20030121191802.GE173@nathan.ruhr.de> In-Reply-To: <200301211651.h0LGp9nS001708@intruder.bmah.org> References: <20030120205441.GC173@nathan.ruhr.de> <200301211651.h0LGp9nS001708@intruder.bmah.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Bruce, On Tue, Jan 21, 2003 at 08:51:09AM -0800, Bruce A. Mah wrote: > The problem with the installation instructions is that the content is > scattered throughout several files and there is not any single > $FreeBSD$ tag you (or anybody) can use to give the latest revision date > for the document as a whole. I hate it when you are right and have to ditch one of my half-cooked ideas into the trashcan. Obviously, adding a visible $FreeBSD$ tag to each file would look... strange. > I *think* you can do this for the installation guide as well, and I > wouldn't object to somebody doing this if it can be made to work. Why do I get the nasty feeling that this will be more complicated than just doing a gigantic cat * > newfile.sgml? > It can't be done for the hardware notes, because there are some MD > files. Which mean that even if I manage to add a usefull publication date to the installation instructions, I am still short of my target of having a way to automatically identify the parts of the rendered release notes that are out of date... short of building them and running diff, that is. /s/Udo -- "41.6: Ersetzen von Austauschen" (HP Color LJ 5M Fehlermeldung) "41.6: Replace Coating Kit" (das englische Original dieser Meldung) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030121191802.GE173>