Re: [PATCH 0/4] memcg: fix memcg resource limit overflow issues

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 2013/7/31 17:34, Jeff Liu wrote:
> On 07/31/2013 04:54 PM, Li Zefan wrote:
> 
>> On 2013/7/31 16:51, Qiang Huang wrote:
>>> On 2013/7/31 16:23, Sha Zhengju wrote:
>>>> Hi list,
>>>>
>>>> On Wed, Jul 31, 2013 at 3:31 PM, Qiang Huang <h.huangqiang@xxxxxxxxxx> wrote:
>>>>> This issue is first discussed in:
>>>>> http://marc.info/?l=linux-mm&m=136574878704295&w=2
>>>>>
>>>>> Then a second version sent to:
>>>>> http://marc.info/?l=linux-mm&m=136776855928310&w=2
>>>>>
>>>>> We contacted Sha a month ago, she seems have no time to deal with it
>>>>> recently, but we quite need this patch. So I modified and resent it.
>>>>
>>>>
>>>> No, I didn't receive any of YOUR message, only a engineer named Libo
>>>> Chen from Huawei connected me recently. I don't approve you to resent
>>>> them on behalf of me, and just before you send this you even don't
>>>> send me a mail. Besides, after a rough look, I do not see any
>>>> innovative ideas from yourself but just rework patches from my last
>>>> version.
>>>> So I'm strong against this patchset.
>>>
>>> Sorry if this troubles you.
>>> Libo Chen is my colleague, we work together, he sent an email to you on
>>> 25 June, to ask about this issue, you said you'll resent it soon, but it
>>> didn't happen until now :(, and he asked again the other day and you didn't
>>> reply. As we really need to fix this problem(and need it in upstream), so
>>> I modified it and sent out.
>>>
>>> I think split patches, rewrite changelogs and tests, they all kind of work
>>> right? Of course, if you mind, I can change it, I just need this fix merged
>>> to upstream ASAP.
>>>
>>> So you want me rewrite this patchset and SOB only you or you want resent this
>>> by yourself? I'm ok with both :)
>>>
>>
>> No, you can't send out patches without your SOB...but you can add a line
>> in the beginning of the email:
>>
>> From: Sha Zhengju <handai.szj@xxxxxxxxxx>
> 
> This is the usual way to credit the original author.  But in this case, Qiang
> should get a confirmation from Sha at first.
> 
> IMO, that would make a mess of a project if anybody can take over an on-going
> task without an approval from the author just because he is looking forward to
> see something will happen on mainline shortly.
> 

This happens from time to time, but mostly it's because of mistakes or lack of
communication or unfamiliarity about the rules rather than deliberatly stealing
someone else's credits.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxx.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>




[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]