From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MlqPG-00050j-NG for qemu-devel@nongnu.org; Thu, 10 Sep 2009 16:38:14 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MlqPB-0004xK-Nc for qemu-devel@nongnu.org; Thu, 10 Sep 2009 16:38:13 -0400 Received: from [199.232.76.173] (port=56095 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MlqPB-0004wl-1J for qemu-devel@nongnu.org; Thu, 10 Sep 2009 16:38:09 -0400 Received: from mx1.redhat.com ([209.132.183.28]:43990) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MlqPA-0008J5-FQ for qemu-devel@nongnu.org; Thu, 10 Sep 2009 16:38:08 -0400 Subject: Re: [Qemu-devel] [PATCH] [RESEND2] Qemu unmaintained? From: Mark McLoughlin In-Reply-To: <4AA9481D.1090508@redhat.com> 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> <1252607396.3403.57.camel@blaa> <4AA9481D.1090508@redhat.com> Content-Type: text/plain Date: Thu, 10 Sep 2009 21:36:59 +0100 Message-Id: <1252615019.3403.75.camel@blaa> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Reply-To: Mark McLoughlin List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Avi Kivity Cc: Amit Shah , Bernhard Kauer , qemu-devel@nongnu.org On Thu, 2009-09-10 at 21:40 +0300, Avi Kivity wrote: > (and we're quite far from catching every regression btw). That's kind of my point. A lot of regressions are only found after they've been pushed. Delaying a push delays finding those regressions. Don't get me wrong - we certainly want to avoid regressions and doing some testing before pushing is a good idea, but there is a balance to be struck. It's also the case that not all patches are equal. It should be possible to short-cut the process for small patches, or regression fixes, or patches from a trusted author who has done significant testing already. Cheers, Mark.