From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:55041) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1S7TAs-0003zx-BN for qemu-devel@nongnu.org; Tue, 13 Mar 2012 10:58:12 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1S7TAi-0006Bt-Fz for qemu-devel@nongnu.org; Tue, 13 Mar 2012 10:58:05 -0400 Received: from mx1.redhat.com ([209.132.183.28]:25102) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1S7TAi-0006BZ-7g for qemu-devel@nongnu.org; Tue, 13 Mar 2012 10:57:56 -0400 Message-ID: <4F5F606C.3040407@redhat.com> Date: Tue, 13 Mar 2012 16:57:48 +0200 From: Avi Kivity MIME-Version: 1.0 References: <4F5E58BE.6040808@weilnetz.de> <4F5E5C49.6060900@codemonkey.ws> <4F5E66A8.5050308@weilnetz.de> <4F5E6809.1000405@codemonkey.ws> <4F5E8774.2010003@suse.de> <4F5E91CA.7040104@codemonkey.ws> <4F5F50BF.2020107@redhat.com> <4F5F5E88.9040601@suse.de> In-Reply-To: <4F5F5E88.9040601@suse.de> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] We need more reviewers/maintainers!! List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: =?UTF-8?B?QW5kcmVhcyBGw6RyYmVy?= Cc: Peter Maydell , Stefano Stabellini , Stefan Weil , Alexander Graf , qemu-devel@nongnu.org, Anthony Liguori On 03/13/2012 04:49 PM, Andreas F=C3=A4rber wrote: > >=20 > > Not at all. I have a memory/core branch and a memory/urgent branch -= - > > it's trivial to maintain them with git, and quite often I send a 1-pa= tch > > pull request. There's no material difference between sending a patch > > and sending a pull request (except if you use git.kernel.org, ugh), a= nd > > it does guarantee you priority handing. > > Actually there is: A trivial fix can be sent with a one-liner: > > $ git send-email HEAD^ Hey, I didn't know about this. Thanks. > whereas there is no matching command for sending a pull request. You > need to manage your own scripts that place git-pull-request output into > the cover letter. (And quite obviously you need a publicly available gi= t > repository in the first place. Most of us do by now.) Implied by being a maintainer. So yes, it takes a little more effort to send a pull request. But it's still pretty easy. --=20 error compiling committee.c: too many arguments to function