Date: Tue, 25 Mar 1997 10:52:36 -0800 (PST) From: Mike Pritchard <mpp> To: wosch@apfel.de (Wolfram Schneider) Cc: wosch@apfel.de, wosch@freefall.freebsd.org, CVS-committers@freefall.freebsd.org, cvs-all@freefall.freebsd.org, cvs-user@freefall.freebsd.org Subject: Re: cvs commit: src/contrib/groff/tmac doc-syms Message-ID: <199703251852.KAA00652@freefall.freebsd.org> In-Reply-To: <199703251113.MAA00863@campa.panke.de> from "Wolfram Schneider" at Mar 25, 97 12:13:50 pm
next in thread | previous in thread | raw e-mail | index | archive | help
Wolfram Schneider wrote: > > Mike Pritchard writes: > >But the .Fx macro isn't really documentation so to speak. > >All that adding releases that will never actually be specified > >as parameters to the macro just results in more code > >for *roff to execute. At least .Fx isn't called that much, > >so it really isn't a big deal. But I can still remember running on > >some older systems where I would groan if I saw the message > >"Formatting page, please wait..." come out, due to the amount of > >time it took to format. > > groff is written in C++ and it is terrible slow. Some hackers > told me groff is 7 times slower than the original troff (C sources) > from AT&T on a SunOS machine. All the more reason not to add unused items to the macro package. > >Maybe we need a releases(7) or history(7) man page to > >document this type of thing. > > I can copy http://www.de.freebsd.org/de/ftp/unix-stammbaum > to /usr/share/misc/bsd-family-tree. I have no objections. Are there any copyright concerns? I'll probably at least write up some type of man page that describes all of the past FreeBSD releases to some degree. -- Mike Pritchard mpp@FreeBSD.org "Go that way. Really fast. If something gets in your way, turn"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199703251852.KAA00652>