From: Fabio M. Di Nitto <fdinitto@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster3 man pages
Date: Thu, 21 Jan 2010 17:52:14 +0100 [thread overview]
Message-ID: <4B58863E.9000304@redhat.com> (raw)
In-Reply-To: <20100121162809.GB12304@redhat.com>
On 1/21/2010 5:28 PM, David Teigland wrote:
> In the process of updating content in my cluster3 man pages, I also tried
> to align the style/structure/etc with this stanard:
>
> http://www.kernel.org/doc/man-pages/online/pages/man7/man-pages.7.html
>
> I think it would be nice to try to sync up all our man pages with those
> conventions, it's been somewhat ad hoc in the past. The following which
> I've updated should be mostly in line with the standard, so you can copy
> bits from them:
would it be possible to have a list of man pages that needs updating
instead? I am not man page expert, nor I have a gigantic interest to
learn the whole standard behind it but I can fix mine if I know they are
broken and what?s broken.
Fabio
next prev parent reply other threads:[~2010-01-21 16:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-21 16:28 [Cluster-devel] cluster3 man pages David Teigland
2010-01-21 16:52 ` Fabio M. Di Nitto [this message]
2010-01-21 17:35 ` David Teigland
2010-01-22 7:29 ` Fabio M. Di Nitto
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B58863E.9000304@redhat.com \
--to=fdinitto@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).