From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mlmma-0002en-JQ for qemu-devel@nongnu.org; Thu, 10 Sep 2009 12:46:04 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MlmmW-0002ck-V1 for qemu-devel@nongnu.org; Thu, 10 Sep 2009 12:46:04 -0400 Received: from [199.232.76.173] (port=37741 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MlmmW-0002cd-Li for qemu-devel@nongnu.org; Thu, 10 Sep 2009 12:46:00 -0400 Received: from mx1.redhat.com ([209.132.183.28]:40093) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MlmmW-0007h1-3b for qemu-devel@nongnu.org; Thu, 10 Sep 2009 12:46:00 -0400 Message-ID: <4AA92D5F.9070205@redhat.com> Date: Thu, 10 Sep 2009 19:46:23 +0300 From: Avi Kivity MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH] [RESEND2] Qemu unmaintained? References: <20090902074905.GB25711@chrom.inf.tu-dresden.de> <20090909121817.GA21997@chrom.inf.tu-dresden.de> <4AA7A6EC.10907@codemonkey.ws> <20090910070336.GD3351@amit-x200.redhat.com> <4AA90592.7080100@codemonkey.ws> <4AA90F7F.2030709@redhat.com> <4AA92122.3050103@codemonkey.ws> <4AA924AE.8060807@redhat.com> <4AA927D8.7000900@codemonkey.ws> <4AA92ADF.80003@redhat.com> <4AA92B7A.7010304@codemonkey.ws> In-Reply-To: <4AA92B7A.7010304@codemonkey.ws> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: Amit Shah , Mark McLoughlin , Bernhard Kauer , qemu-devel@nongnu.org On 09/10/2009 07:38 PM, Anthony Liguori wrote: > Avi Kivity wrote: >> On 09/10/2009 07:22 PM, Anthony Liguori wrote: >>>> You certainly shouldn't ack patches you don't commit! >>> >>> >>> But most spend time in staging. >> >> What's the percentage of patches that make it to master? For me it's >> >90%. If it's too low we nned to fix that. > > Closer to 20% I'd say. This is largely due to multiple versions of > the same series. If there's a way to improve this, that would make my > life a lot easier. Well, I'd say this is much more important than acking patches (though if you acked and unacked patches, it would be a lot more visible, and might shame the submitters into increased care). Why are there multiple series? If you have comments, clearly you wouldn't stage the patches. If others have comments, then you can simply wait a few days before staging (this is what I do). If testing fails, well, that's what testing is for. If the submitter puts out a new version, well, no good answer to that. Ask for an incremental? > Well the question is, should I/you edit this, or reject the patch > requesting a better changelog? > > Certainly, the later is what akpm often does. I'm happy to reject patches for whitespace but I will edit changelogs. My rationale is that many people don't care about that and I can't make them care; further the log is mostly for my own benefit - I spend quite a lot of time reading it when hunting regressions or preparing patchqueues for upstream. -- I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain.