Re: Getting rid of standard boiler plate in kernel man pages CODE REFERENCES

2010-11-08 Thread Thomas Klausner
Hi Iain! I'm not sure what you are proposing.. can you show an example diff (eg using bluetooth.9) ? Sure, attached. Thomas Index: bluetooth.9 === RCS file: /cvsroot/src/share/man/man9/bluetooth.9,v retrieving revision 1.4 diff

Re: Getting rid of standard boiler plate in kernel man pages CODE REFERENCES

2010-11-08 Thread Paul Goyette
On Mon, 8 Nov 2010, David Holland wrote: Not from me! Although rather than /usr/src it might say the top level of the source tree. How about: [...] +Any paths are relative to the top level of the source tree (usually +.Pa /usr/src ) . Sounds fine. Or perhaps historically instead of

Re: Getting rid of standard boiler plate in kernel man pages CODE REFERENCES

2010-11-08 Thread Mindaugas Rasiukevicius
Thomas Klausner w...@netbsd.org wrote: Many many many kernel (section 9) man pages contain the following sentence in their CODE REFERENCES section: This section describes places within the .Nx source tree where actual code implementing .Nm can be found. All pathnames are relative to

Re: Getting rid of standard boiler plate in kernel man pages CODE REFERENCES

2010-11-08 Thread Mindaugas Rasiukevicius
Paul Goyette p...@whooppee.com wrote: How about: [...] +Any paths are relative to the top level of the source tree (usually +.Pa /usr/src ) . Sounds fine. Or perhaps historically instead of usually :) Or often might work, too. No opinion on that :-) typically or

Getting rid of standard boiler plate in kernel man pages CODE REFERENCES

2010-11-07 Thread Thomas Klausner
Hi! Many many many kernel (section 9) man pages contain the following sentence in their CODE REFERENCES section: This section describes places within the .Nx source tree where actual code implementing .Nm can be found. All pathnames are relative to .Pa /usr/src . .Pp I suggest we remove it