From: David Teigland <teigland@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster3 man pages
Date: Thu, 21 Jan 2010 10:28:09 -0600 [thread overview]
Message-ID: <20100121162809.GB12304@redhat.com> (raw)
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:
cluster.conf
dlm_tool
dlm_controld
gfs_control
gfs_controld
group_tool
groupd
fence_node
fence_tool
fenced
fence_ack_manual
One other advantage of doing this is that we should be able to use the
same tools to build online versions of the man pages as is done for the
man-pages project,
http://www.kernel.org/doc/man-pages/online/dir_all_by_section.html
next reply other threads:[~2010-01-21 16:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-21 16:28 David Teigland [this message]
2010-01-21 16:52 ` [Cluster-devel] cluster3 man pages Fabio M. Di Nitto
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=20100121162809.GB12304@redhat.com \
--to=teigland@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).