From: Fabio M. Di Nitto <fdinitto@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] How to provide documentation feedback and patches?
Date: Wed, 19 Oct 2011 14:52:52 +0200 [thread overview]
Message-ID: <4E9EC824.40900@redhat.com> (raw)
In-Reply-To: <CAFm_bUi_E4dfcLXo_UtK7bdWk20dTPQ5ZDvjVndwrE8Yv9FA9w@mail.gmail.com>
Hi Arnaud,
On 10/19/2011 1:43 PM, Arnaud Quette wrote:
> Hi Cluster-devel,
>
> A quick question for which I've not found an answer yet:
> how / where should I send contribution or discuss cluster-devel related topics?
patches/contribution should go to cluster-devel
normal user discussion should go to linux-cluster mailing list.
> More specifically, I would like to add the Eaton supported devices for
> Fence agents to this doc:
> https://access.redhat.com/kb/docs/DOC-30004
You can?t do it directly :) you need to file a bugzilla and we will
forward it to the documentation guys.
Also note that fence_eaton is not shipped in RHEL.
Fabio
next prev parent reply other threads:[~2011-10-19 12:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-19 11:43 [Cluster-devel] How to provide documentation feedback and patches? Arnaud Quette
2011-10-19 12:49 ` Lon Hohberger
2011-10-19 12:52 ` Fabio M. Di Nitto [this message]
2011-10-20 8:09 ` Arnaud Quette
2011-10-20 8:12 ` 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=4E9EC824.40900@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 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.