From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752846Ab3GQJRf (ORCPT ); Wed, 17 Jul 2013 05:17:35 -0400 Received: from aserp1040.oracle.com ([141.146.126.69]:35180 "EHLO aserp1040.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751786Ab3GQJRd (ORCPT ); Wed, 17 Jul 2013 05:17:33 -0400 Message-ID: <51E660C6.1020409@oracle.com> Date: Wed, 17 Jul 2013 17:15:50 +0800 From: Jeff Liu User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20120410 Thunderbird/11.0.1 MIME-Version: 1.0 To: Steven Rostedt CC: Sarah Sharp , David Lang , ksummit-2013-discuss@lists.linuxfoundation.org, Greg Kroah-Hartman , Darren Hart , Olivier Galibert , stable , Linux Kernel Mailing List , Willy Tarreau , Linus Torvalds , Ingo Molnar Subject: Re: [Ksummit-2013-discuss] [ATTEND] How to act on LKML References: <20130715204135.GH15531@xanatos> <1373926109.17876.221.camel@gandalf.local.home> <20130715223615.GI15531@xanatos> <20130716211235.GG4994@xanatos> <20130716212704.GB9371@thunk.org> <20130716224357.GK4994@xanatos> <1374015299.6458.76.camel@gandalf.local.home> <20130716231217.GL4994@xanatos> <51E5E609.1030202@oracle.com> <1374022296.6458.118.camel@gandalf.local.home> In-Reply-To: <1374022296.6458.118.camel@gandalf.local.home> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Source-IP: ucsinet21.oracle.com [156.151.31.93] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 07/17/2013 08:51 AM, Steven Rostedt wrote: > On Wed, 2013-07-17 at 08:32 +0800, Jeff Liu wrote: > >> Another thing might deviated from the main theme, but I'd like to raise it >> here because I would like to see what's the proper way for that. >> >> For instance, people A posted a patch set to the mailing list at first, >> people B think that there are some issues in A's implementation, and he >> happened to play around the same stuff recently, so he submitted another >> patch series. Finally, people B made it. >> (In that period, people A kept silent, maybe because he/she was unhappy) >> >> This is a actual occurrence I once observed from a subsystem list(my >> apologies, I just want to talk this case rather than against somebody), >> it seems people A is a new comer(because I can not searched any past >> commits of him/her from the git log), people B is definitely a senior guy. >> >> So that's my question, is that a proper collaboration form in kernel >> community? Does it better if people B could give some suggestions to >> help A to improve the code, especially if those help would help A stepping >> into the kernel development -- maybe it's depend largely on one's opinion. :( > > This is a completely different issue from the one in this thread, but it > is also a legitimate issue and honestly, a bigger one than perceived > insults. > > Is it proper collaboration? Absolutely not. Something that I try to be > sensitive to as it's something I can do as well. There's been things on > my todo list, where someone would send me patches that do it. I would be > thinking "darn it, I wanted to do it" and even worse, the patches that > were sent wouldn't be of the way I wanted them. But I've tried to be > good, and instead of just going about and implementing it myself, I > would try to help the person massage the patches into what I wanted. It's kind of you. Generally, most forks are nice enough in helping others. Actually, I only noticed once of something like that the year before. Well, I just received an offline email from my college a fews hours ago as she checked this topic and unfortunately, she has experienced the same thing a few days ago. > That takes a lot of effort and discipline, and honestly, helping someone > else do the work you wanted is much harder than just doing it yourself. Exactly, so I always appreciate the patch reviewers. Thanks, -Jeff > > Sometimes the maintainer just takes the easier route, and does the work > themselves (because it's also more fun too). But that's really a slap in > the face of the person that submitted the work in the first place. If > anything hurts the community, it's this behavior. Not Linus giving > someone an ass wipe. > > -- Steve > >