From: Stefan Weil <sw@weilnetz.de>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
qemu-devel@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] We need more reviewers/maintainers!!
Date: Mon, 12 Mar 2012 22:41:57 +0100 [thread overview]
Message-ID: <4F5E6DA5.3000505@weilnetz.de> (raw)
In-Reply-To: <4F5E6712.2040501@codemonkey.ws>
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<anthony@codemonkey.ws>
>>>> 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
next prev parent reply other threads:[~2012-03-12 21:42 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-12 17:06 [Qemu-devel] We need more reviewers/maintainers!! Stefano Stabellini
2012-03-12 17:16 ` Anthony Liguori
2012-03-12 17:34 ` Stefano Stabellini
2012-03-12 18:48 ` Anthony Liguori
2012-03-12 19:10 ` Stefano Stabellini
2012-03-12 19:04 ` Anthony Liguori
2012-03-12 19:21 ` Stefano Stabellini
2012-03-12 19:38 ` Anthony Liguori
2012-03-13 11:34 ` Stefano Stabellini
2012-03-13 11:27 ` Kevin Wolf
2012-03-13 11:41 ` Stefano Stabellini
2012-03-13 12:12 ` Paolo Bonzini
2012-03-12 18:03 ` Lluís Vilanova
2012-03-12 18:10 ` Anthony Liguori
2012-03-12 19:39 ` Lluís Vilanova
2012-03-12 19:43 ` Anthony Liguori
2012-03-12 18:18 ` Stefano Stabellini
2012-03-13 13:27 ` Avi Kivity
2012-03-14 13:50 ` Andreas Färber
2012-03-14 13:52 ` Anthony Liguori
2012-03-14 13:58 ` Peter Maydell
2012-03-14 14:17 ` Anthony Liguori
2012-03-14 14:25 ` Andreas Färber
2012-03-13 10:38 ` Andreas Färber
2012-03-12 19:18 ` Michael Roth
2012-03-13 11:11 ` Stefano Stabellini
2012-03-12 20:12 ` Stefan Weil
2012-03-12 20:24 ` Peter Maydell
2012-03-12 20:29 ` Anthony Liguori
2012-03-12 20:43 ` Peter Maydell
2012-03-12 21:06 ` Anthony Liguori
2012-03-12 21:09 ` malc
2012-03-12 21:13 ` Anthony Liguori
2012-03-12 21:41 ` Stefan Weil [this message]
2012-03-12 21:52 ` Anthony Liguori
2012-03-12 21:43 ` malc
2012-03-12 21:49 ` Anthony Liguori
2012-03-12 22:53 ` malc
2012-03-12 21:16 ` Peter Maydell
2012-03-12 21:19 ` Anthony Liguori
2012-03-13 10:39 ` Stefan Hajnoczi
2012-03-12 20:40 ` Michael S. Tsirkin
2012-03-12 20:27 ` Anthony Liguori
2012-03-12 21:12 ` Stefan Weil
2012-03-12 21:18 ` Anthony Liguori
2012-03-12 23:32 ` Andreas Färber
2012-03-13 0:16 ` Anthony Liguori
2012-03-13 0:54 ` Alexander Graf
2012-03-13 1:01 ` Andreas Färber
2012-03-13 1:23 ` Alexander Graf
2012-03-13 1:31 ` Super Bisquit
2012-03-13 1:39 ` Anthony Liguori
2012-03-13 2:04 ` Alexander Graf
2012-03-13 2:05 ` Anthony Liguori
2012-03-14 19:47 ` Blue Swirl
2012-03-13 9:09 ` Peter Maydell
2012-03-13 13:50 ` Avi Kivity
2012-03-13 14:12 ` Peter Maydell
2012-03-13 14:39 ` Avi Kivity
2012-03-13 14:43 ` Anthony Liguori
2012-03-13 14:46 ` Alexander Graf
2012-03-13 14:54 ` Peter Maydell
2012-03-13 14:49 ` Andreas Färber
2012-03-13 14:57 ` Avi Kivity
2012-03-13 15:13 ` Eric Blake
2012-03-12 21:24 ` Stefan Weil
2012-03-13 13:40 ` Avi Kivity
2012-03-13 14:00 ` Anthony Liguori
2012-03-13 14:38 ` Avi Kivity
2012-03-13 14:41 ` Anthony Liguori
2012-03-14 20:00 ` Blue Swirl
2012-03-14 19:55 ` Blue Swirl
2012-03-13 10:41 ` Stefan Hajnoczi
2012-03-13 16:31 ` Andreas Färber
2012-03-13 18:14 ` Stefan Weil
2012-03-14 9:17 ` Stefan Hajnoczi
2012-07-18 9:28 ` Peter Maydell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F5E6DA5.3000505@weilnetz.de \
--to=sw@weilnetz.de \
--cc=anthony@codemonkey.ws \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefano.stabellini@eu.citrix.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).