From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:51634) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TxF1g-0003Bo-Uw for qemu-devel@nongnu.org; Mon, 21 Jan 2013 05:54:54 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TxF1f-0005W5-Pl for qemu-devel@nongnu.org; Mon, 21 Jan 2013 05:54:52 -0500 Received: from mail-bk0-f52.google.com ([209.85.214.52]:44229) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TxF1f-0005W0-J1 for qemu-devel@nongnu.org; Mon, 21 Jan 2013 05:54:51 -0500 Received: by mail-bk0-f52.google.com with SMTP id y7so185018bkt.39 for ; Mon, 21 Jan 2013 02:54:50 -0800 (PST) Date: Mon, 21 Jan 2013 11:54:46 +0100 From: Stefan Hajnoczi Message-ID: <20130121105446.GA10400@stefanha-thinkpad.redhat.com> References: <50F95294.1000400@gmail.com> <20130118140619.GA28079@stefanha-thinkpad.redhat.com> <50FC6376.2050903@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <50FC6376.2050903@gmail.com> Subject: Re: [Qemu-devel] [Qemu-trivial] [PATCH v2] configure: silence pkg-config's check for curses List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Vadim Evard Cc: qemu-devel@nongnu.org On Mon, Jan 21, 2013 at 01:36:54AM +0400, Vadim Evard wrote: > By the way (sorry if this was discussed before and is a strong > decision) I'd say e-mail based workflow is of course very flexible - > and very very novice-unfriendly. Dash, I had to learn git commands > I'd never use in my usual workflow with local or Github repos. And, > well, I was not very good with that. 10 ways with 10 options in > each. You all saw my previous patch mail with "fubar" header and no > signed-off-by string. > > Is there a reason you (team) don't use e.g. Github at least for > trivial patches? Yes, the email-based approach is the most flexible but also has a learning curve. For one-time contributors it can seem like wasted effort. The QEMU community is familiar with the email-based workflow and has customized it. One key idea is that all patches go through qemu-devel@nongnu.org - even trivial patches are exposed to code review from the whole community. A new vector for code submission still needs to keep this property. For another open source project that I'm involved in I have set up a cronjob that sends GitHub pull requests to the project mailing list. This way the mailing list still sees all patches before they get committed. Replying to patches doesn't work though - you still need to log into GitHub in order to send comments to the author. I can't ask all QEMU developers to do that. Any ideas how to make GitHub work with QEMU? Stefan