From: Eric Ren <zren@suse.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [Ocfs2-tools-devel] ocfs2 tools
Date: Thu, 17 Mar 2016 14:37:48 +0800 [thread overview]
Message-ID: <56EA50BC.4050608@suse.com> (raw)
In-Reply-To: <56E2F31F020000F90002D5C7@prv-mh.provo.novell.com>
> Hello Mark,
>
> Could you help to add these accounts in ocfs2-tools project on github?
>
> Gang He - SUSE: ganghe
> Junxiao - Oracle: biger410
> Joseph Qi - Huawei: josephhz
Maybe, we can also create an ocfs2 organization on github;-)
And I'm thinking of if we can have an IRC channel. I've create
channel#ocfs2 on freenode, you can
login through website[1], or Thunderbird[2]. Welcome!
[1] https://webchat.freenode.net/
[2] Thunderbird -> cat -> irc -> freenode(default)->your nickname->irc
connected->join chat->#ocfs2
Eric
>
>
> Thanks
> Gang
>
>
>> On 2016/3/3 9:43, Gang He wrote:
>>> Hello All,
>>>
>>> Thanks for Goldwyn's suggestion, I agree.
>>> My github ID is ganghe.
>>>
>>> Thanks
>>> Gang
>>>
>>>
>>>> On 03/01/2016 09:13 PM, Mark Fasheh wrote:
>>>>> On Wed, Mar 02, 2016 at 10:50:20AM +0800, Joseph Qi wrote:
>>>>>> Hi Gang,
>>>>>> Thanks for your reply.
>>>>>> How's the plan to pick up those missed patches?
>>>>> They need review on the mailing list. I've barely got time for kernel review
>>>>> these days so I was hoping some of you all could handle some of that. As far
>>>>> as getting it into the actual repository, I can add committers to the
>>>>> project as we need them.
>>>> I agree. I am pretty busy with other responsibilities.
>>>> I propose the following reviewers/committers from each organizations:
>>>>
>>>> Gang He - SUSE
>>>> Junxiao - Oracle
>>>> Joseph Qi - Huawei
>>>>
>>>> If you agree to maintain, please send in your github id's. Or else if
>>>> you have objections or are too busy, you may propose another name.
>> Agree. My github id is josephhz.
>>
>> Thanks,
>> Joseph
>>>>
>>>>
>>>>> But regardless, the patches have to be reviewed, even if the person
>>>>> reviewing is the one eventually committing.
>>>>>
>>>> Yes, and I hope sob and reviewed by are from different organizations so
>>>> a single organization does not take away the code.
>>>>
>>>> --
>>>> Goldwyn
>>>
>>> .
>>>
>
> _______________________________________________
> Ocfs2-tools-devel mailing list
> Ocfs2-tools-devel at oss.oracle.com
> https://oss.oracle.com/mailman/listinfo/ocfs2-tools-devel
>
next parent reply other threads:[~2016-03-17 6:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <56D64637.70607@huawei.com>
[not found] ` <56D6BA89020000F90002BF28@prv-mh.provo.novell.com>
[not found] ` <56D654EC.8080604@huawei.com>
[not found] ` <20160302031326.GJ1239@wotan.suse.de>
[not found] ` <56D7163F.4070900@suse.de>
[not found] ` <56D8074C020000F90002C1E6@prv-mh.provo.novell.com>
[not found] ` <56D7A284.1030101@huawei.com>
[not found] ` <56E2F31F020000F90002D5C7@prv-mh.provo.novell.com>
2016-03-17 6:37 ` Eric Ren [this message]
2016-03-17 7:02 ` [Ocfs2-devel] [Ocfs2-tools-devel] ocfs2 tools Gang He
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=56EA50BC.4050608@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 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.