From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:42552) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1S7D0X-0006sI-Hg for qemu-devel@nongnu.org; Mon, 12 Mar 2012 17:42:22 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1S7D0D-0007oi-A7 for qemu-devel@nongnu.org; Mon, 12 Mar 2012 17:42:21 -0400 Received: from v220110690675601.yourvserver.net ([78.47.199.172]:43111) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1S7D0D-0007oR-1A for qemu-devel@nongnu.org; Mon, 12 Mar 2012 17:42:01 -0400 Message-ID: <4F5E6DA5.3000505@weilnetz.de> Date: Mon, 12 Mar 2012 22:41:57 +0100 From: Stefan Weil MIME-Version: 1.0 References: <4F5E58BE.6040808@weilnetz.de> <4F5E5CA4.3040407@codemonkey.ws> <4F5E6572.5060604@codemonkey.ws> <4F5E6712.2040501@codemonkey.ws> In-Reply-To: <4F5E6712.2040501@codemonkey.ws> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] We need more reviewers/maintainers!! List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: Peter Maydell , Stefano Stabellini , qemu-devel@nongnu.org, "Michael S. Tsirkin" Am 12.03.2012 22:13, schrieb Anthony Liguori: > On 03/12/2012 04:09 PM, malc wrote: >> On Mon, 12 Mar 2012, Anthony Liguori wrote: >> >>> On 03/12/2012 03:43 PM, Peter Maydell wrote: >>>> On 12 March 2012 20:29, Anthony Liguori >>>> wrote: >>>>> On 03/12/2012 03:24 PM, Peter Maydell wrote: >>>>>> I agree that that's a specific area it would be nice to do >>>>>> better in. It seems to me that the qemu-trivial process for >>>>>> sweeping up trivial patches has been working well; maybe we >>>>>> could use a slightly more formal qemu-urgent process for >>>>>> flagging up build breakage etc? >>>>>> >>>>>> (Personally I'd support a rule that any outstanding >>>>>> build-breakage fixes must always go in before anything else.) >>>>> >>>>> >>>>> When are build-breakage fixes not trivial? >>>> >>>> 'trivial' implies "it's OK if this patch doesn't go in for a >>>> week or two until the trivial patch queue has built up to >>>> a reasonable size". Also sending them via trivial means >>>> there's no mechanism for causing them to be applied before >>>> other commits/pullreqs. So generally I don't cc build-fixes to >>>> trivial. >>> >>> In all fairness, the last build breakage I see was specific to >>> win32, was >>> reported on Mar 1st, and a patch was committed on Mar 3rd. >>> >>> I don't think it's reasonable to expect more than this for a >>> breakage on >>> win32. >> >> Why? > > Patch came on a Thursday and was applied on a Saturday. That's pretty > much one business day. > > For a problem that affects very few people (and hence has very few > people complaining), it seems like a reasonable response time. Do you have numbers? As far as I know, more people are using Windows than Linux. Ok, there are more QEMU developers which work on Linux than on Windows, but that's no reason why w32 build fixes are less important. Many Linux developers will simply fix a broken build in their local tree. Windows developers expect that everything works out of the box, without manually changing the source code. => All patches which fix broken build are equal. > Regards, > > Anthony Liguori