The state of some of the man pages
bcr at FreeBSD.org
Wed Dec 7 21:16:06 UTC 2011
-----BEGIN PGP SIGNED MESSAGE-----
Am 07.12.11 21:23, schrieb Frank Leonhardt:
> I've been moved to join this list because some of the man pages are
> driving me crazy; they're out of date.
> Fortunately I speak fluent 'C', so I often end up diving into the source
> code in order to find out what's really going on. But I'm currently in
> the mood to do something more positive about it.
> But how?
> I'm not talking about fixing typos here; I'm referring to large chunks
> of information that are simply missing. For example, 'top' does so much
> more than the current documentation suggests.
> If someone would be good enough to tell me how, I'm volunteering to
> update the man pages as I go.
> For the avoidance of doubt, I don't want to know how to create a man
> page, I want to know how to submit updated man pages for eventual
> inclusion in the next release.
> Thanks, Frank.
thanks for your offer to help. You can send bug reports containing
unified diffs (against HEAD sources) to our problem report database. You
can find it on the FreeBSD.org website under Support, Submit Bug-report
or via this direct link:
Fill out the fields with as much information as possible as this will
more likely draw someone's attention. Before you submit anything though,
check whether the problem hasn't been reported yet by searching our bug
If there is a PR already covering your problem, you can submit a
follow-up with a patch attached to bring the issue forward.
Feel free to ask if anything is not clear.
FreeBSD Documentation Committer
The FreeBSD Documentation Project
FreeBSD German Documentation Project - https://doc.bsdgroup.de
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-----END PGP SIGNATURE-----
More information about the freebsd-doc