From: Fabio M. Di Nitto <fabbione@fabbione.net>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Fix fence-agents manpages
Date: Tue, 06 Dec 2011 16:13:41 +0100 [thread overview]
Message-ID: <4EDE3125.2070501@fabbione.net> (raw)
In-Reply-To: <CAFm_bUhiySRvMzh3wYXCAWme5-U7E4nfQ25Q2d-QiMR-9=YS3Q@mail.gmail.com>
On 12/6/2011 4:05 PM, Arnaud Quette wrote:
> Hi Fabio,
>
> 2011/12/6 Fabio M. Di Nitto <fabbione@fabbione.net>:
>> On 12/6/2011 2:27 PM, Arnaud Quette wrote:
>>> Hi Cluster-devel list,
>>>
>>> You will find attached a patch originating from Ubuntu (Andres
>>> Rodriguez), that fixes a few issues in manpages (namely fence_drac and
>>> fence_scsi).
>>
>>
>> I wonder why the ubuntu/canonical maintainers can?t post patches
>> directly for upstream inclusion.
>
> they obviously can Fabio.
> But I proposed to do this on my side, since I still have some things
> to do around fence_eaton...
> That way, they can focus on other things.
>
> After all, it's just posting an email. The actual and important work
> is to catch bugs and fix this ;-)
>
>>> Please consider applying it.
>>>
>>> As a side note, you may want to consider Asciidoc [1] to handle
>>> generation of manpages, in groff and html format.
>>> This already takes care of the groff formating, and would avoid the
>>> above kind of issues.
>>> That said, iirc you're also doing some POD style extraction, so it may
>>> not be fully relevant.
>>
>> goal is to have all manpages generated at build time via fence_agent -o
>> metadata output. Most of patches already exists for those few agents
>> that don?t it.
>
> ok, that confirms the "POD" style approach.
> I wasn't sure if you were standardizing on this, or going away from.
The patch will be "obsoleted" in the fence-agents release or max two.
Fabio
next prev parent reply other threads:[~2011-12-06 15:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-06 13:27 [Cluster-devel] Fix fence-agents manpages Arnaud Quette
2011-12-06 13:43 ` Fabio M. Di Nitto
2011-12-06 15:05 ` Arnaud Quette
2011-12-06 15:13 ` Fabio M. Di Nitto [this message]
2011-12-07 8:53 ` Arnaud Quette
2011-12-07 8:54 ` 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=4EDE3125.2070501@fabbione.net \
--to=fabbione@fabbione.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.