From: Eric Ren <zren@suse.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] Welcome to join in: an ocfs2 IRC channel is setup for quick communications
Date: Mon, 4 Apr 2016 20:14:42 +0800 [thread overview]
Message-ID: <57025AB2.8040904@suse.com> (raw)
In-Reply-To: <5702525C.9090706@suse.de>
Hello Goldwyn,
On 04/04/2016 07:39 PM, Goldwyn Rodrigues wrote:
> Hello Eric,
>
> On 04/01/2016 08:50 PM, Eric Ren wrote:
>> Hello Mark and all,
>>
>> Last week, I proposed to have an IRC channel for OCFS2 in tools maillist
>> [1]. I'm afraid most people probably didn't even notice it.
>
>
> There is an ocfs2 channel in zeniv.linux.org.uk.
Thanks for your heads up. I failed to join in with #ocfs2 without
password. If it needs password,
what is it? Or I'm wrong with the channel name?
It would help a lot if we can explicitly record a IRC on official website;-)
Eric
next prev parent reply other threads:[~2016-04-04 12:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-02 1:50 [Ocfs2-devel] Welcome to join in: an ocfs2 IRC channel is setup for quick communications Eric Ren
2016-04-04 8:02 ` Gang He
2016-04-04 11:39 ` Goldwyn Rodrigues
2016-04-04 12:14 ` Eric Ren [this message]
2016-04-05 13:00 ` Goldwyn Rodrigues
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=57025AB2.8040904@suse.com \
--to=zren@suse.com \
--cc=ocfs2-devel@oss.oracle.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).