Date: Mon, 8 Jul 2002 13:06:22 -0700 (PDT) From: Julian Elischer <julian@elischer.org> To: John Baldwin <jhb@FreeBSD.org> Cc: Julian Elischer <julian@FreeBSD.org>, cvs-all@FreeBSD.org, cvs-committers@FreeBSD.org Subject: RE: cvs commit: src/share/man/man9 thread_exit.9 Message-ID: <Pine.BSF.4.21.0207081304010.29644-100000@InterJet.elischer.org> In-Reply-To: <XFMail.20020708154617.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
The advantage to having one page per function is that teh xref stuff works better, and give thread_exit() in code in front of me, I don't hav eto try guess what it will be under... of course these are rather lame excusses given multiply linked man pages and man -k. On Mon, 8 Jul 2002, John Baldwin wrote: > > On 08-Jul-2002 Julian Elischer wrote: > > julian 2002/07/08 00:51:20 PDT > > > > Added files: > > share/man/man9 thread_exit.9 > > Log: > > Add a man page. Style comments welcome. I have a bunch-o-new-pages > > to add so I might as we find out what I did wrong now :-) > > I would just have a single thread.9 manpage much like we have a single > ucred.9, kthread.9 (bad name), mutex.9, etc. It makes it easier when > you can discuss a subsystem as a whole and then describe each function > within that context rather than scattering it across a bunch of different > manpages. However, that is a matter of opinion. The new-bus manpages > are an example of using one page per function. Personally I find them > a bit hard to follow as a result. :-P > > -- > > John Baldwin <jhb@FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/ > "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0207081304010.29644-100000>