From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:44189) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cefVq-0008P8-Bm for qemu-devel@nongnu.org; Fri, 17 Feb 2017 05:11:39 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cefVn-0000Si-71 for qemu-devel@nongnu.org; Fri, 17 Feb 2017 05:11:38 -0500 Date: Fri, 17 Feb 2017 18:11:31 +0800 From: Fam Zheng Message-ID: <20170217101131.GA3468@lemon.lan> References: <1933406e-2576-e687-3545-a72f3b999310@redhat.com> <20170217064327.GB21716@lemon.lan> <2a2570bf-2e4b-e793-4362-0a679b182b1e@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2a2570bf-2e4b-e793-4362-0a679b182b1e@redhat.com> Subject: Re: [Qemu-devel] Fix build break during configuration on musl-libc based Linux systems. List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Laszlo Ersek Cc: Chad Joan , qemu-trivial@nongnu.org, Paolo Bonzini , qemu-devel@nongnu.org On Fri, 02/17 10:23, Laszlo Ersek wrote: > On 02/17/17 07:43, Fam Zheng wrote: > > On Thu, 02/16 12:47, Chad Joan wrote: > >> I am glad others are chiming in and might provide better solutions. > >> > >> Honestly, following the instructions at > >> http://wiki.qemu-project.org/Contribute/SubmitAPatch to-the-letter is quite > >> daunting to me, just to get one line of code changed. It might help if > >> that page had some kind of dead-simple example for trivial patches; > >> something like: > >> $ cd > >> $ git format-patch blah blah blah > >> $ maybe-some-other-command > >> $ # Now copy the contents of file xyz.patch into your email client and send > >> to qemu-devel@nongnu.org and qemu-trivial@nongnu.org > > > > Makes sense in general except for the sending part - email clients tend to > > damage the patch when you copy and paste by wrapping long lines or messing up > > other things. But your point is taken, we should make the first (or a one-shot) > > contribution as easy as possible. > > I disagree (from the sidelines, that is; I'm not a QEMU maintainer -- > I'm a co-maintainer elsewhere). The patch submission process exists for > a reason, the goal is to maximize the throughput of long-term > contributors and maintainers, because that's the best for the project's > overall health and progress. Having a process and smoothly revealing it to new contributors are not in conflict. The problem here is the long SubmitAPatch I think. It does include more details than needed for the minimum of the very first submission; also it is not in an easy-to-follow step-by-step form. I believe people will happily learn the process once he feels appreciation on his effort, once they get replies to his patch. :) > > It does not mean that one-off contributions are not welcome -- all > contributions are welcome that follow the process (and beyond that, > everyone is welcome to become a long-term contributor). IMHO one-off _fixes_ are also good, like this one. Like Peter noted, the only recommendation for those who don't like formalities and have no intention to contribute regularly, is to add a "signed-off-by" line to their patch. > > Just my two cents, of course; don't take this as an official standpoint > or whatever. (And, I'm saying this after having manually fixed up > garbled patches from one-off contributors.) > > Laszlo Fam