From: Fabio M. Di Nitto <fdinitto@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] How to provide documentation feedback and patches?
Date: Thu, 20 Oct 2011 10:12:53 +0200 [thread overview]
Message-ID: <4E9FD805.9040407@redhat.com> (raw)
In-Reply-To: <CAFm_bUiuOQp_TwPXAqdn_-M2-SCFtvt0Nphw9-tgU9oovFnDfA@mail.gmail.com>
On 10/20/2011 10:09 AM, Arnaud Quette wrote:
> Hi Fabio and Lon,
>
> first, thanks for your answers.
>
> 2011/10/19 Fabio M. Di Nitto:
>> 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.
>
> that was the obvious part, but reading back my question, I was not
> that clear ;-)
>
> I'll have some more patches for you in a month or so... and some questions too.
Just send the patches/devel related questions to cluster-devel and Marek.
Fabio
prev parent reply other threads:[~2011-10-20 8:12 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
2011-10-20 8:09 ` Arnaud Quette
2011-10-20 8:12 ` Fabio M. Di Nitto [this message]
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=4E9FD805.9040407@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.