From owner-freebsd-doc@FreeBSD.ORG Wed Dec 7 21:16:06 2011 Return-Path: Delivered-To: freebsd-doc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 894C7106564A for ; Wed, 7 Dec 2011 21:16:06 +0000 (UTC) (envelope-from bcr@FreeBSD.org) Received: from mxout1.bln1.prohost.de (mxout1.bln1.prohost.de [213.160.84.47]) by mx1.freebsd.org (Postfix) with ESMTP id 192288FC08 for ; Wed, 7 Dec 2011 21:16:05 +0000 (UTC) Received: from Benedicts-Macbook-Pro.local (p4FC71AC3.dip.t-dialin.net [79.199.26.195]) (authenticated bits=0) by mx1.bln1.prohost.de (8.14.1/8.14.1) with ESMTP id pB7LFvQV022216 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 7 Dec 2011 22:15:58 +0100 Message-ID: <4EDFD794.3070102@FreeBSD.org> Date: Wed, 07 Dec 2011 22:16:04 +0100 From: Benedict Reuschling Organization: The FreeBSD Project User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:8.0) Gecko/20111105 Thunderbird/8.0 MIME-Version: 1.0 To: freebsd-doc@FreeBSD.org References: <4EDFCB27.3030803@fjl.co.uk> In-Reply-To: <4EDFCB27.3030803@fjl.co.uk> X-Enigmail-Version: 1.3.3 OpenPGP: id=4A819348 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Null-Tag: 64a31e7e7e918a68a85d595f6e98c99f Cc: Subject: Re: The state of some of the man pages X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: bcr@FreeBSD.org List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Dec 2011 21:16:06 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 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. Hello 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: http://www.freebsd.org/send-pr.html 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 database: http://www.freebsd.org/cgi/query-pr-summary.cgi?query 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. Regards Benedict Reuschling 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/ iEYEARECAAYFAk7f15QACgkQTSZQLkqBk0htFACdF2HXhv7uK45hTRDlq/F5aKs9 TBQAoLuRS0oo8gZwvWuEfynPCPEh9kQr =g2TU -----END PGP SIGNATURE-----