The state of some of the man pages

[Johann Kois]

Hello Frank,

that sounds great.

the correct procedure for that would be to create patches and send them 
in via send-pr.  This way they will be registered in our "problem report 
database (GNATS) and won't get lost.  A committer will then check them 
and (if they are fine) commit them.  This way they will be included in 
the next release.

For more information on how to create/send PR (problem reports) please 
read the article "Writing FreeBSD Problem Reports" under 
http://www.freebsd.org/doc/en/articles/problem-reports/index.html and 
maybe "Problem Report Handling Guidelines" for some technical information.

Regards.

Johann

-- 
  Johann Kois
  jkois(at)FreeBSD.org
  FreeBSD Documentation Project
  FreeBSD German Documentation Project - https://doc.bsdgroup.de


"On 12/07/2011 21:23, Frank Leonhardt wrote:
> 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.
>
> _______________________________________________
> freebsd-doc at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-doc
> To unsubscribe, send any mail to "freebsd-doc-unsubscribe at freebsd.org"
>