qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] An organizational suggestion


From: Ian Jackson
Subject: Re: [Qemu-devel] An organizational suggestion
Date: Tue, 3 Jun 2008 16:27:37 +0100

Jamie Lokier writes ("Re: [Qemu-devel] An organizational suggestion"):
> It's the Linus Torvalds school of flow control.  If you don't get a
> reply, try again.

I see.  That seems rather rude to me, so I don't do it.  Am I really
supposed to keep a list of my outstanding patches and retransmit them
like some kind of bandwidth-hogging peer-to-peer application ?

If everyone did that, then the number of patches accepted would go
down rather than up, surely ?  Because everyone would be spending
their time wading through all these resends, rather than paying
attention to the content.

Also - implicit in your comment that it's a form of `flow control' is
that it's caused by a lack of upstream capacity.  I think that part is
very true.  We do have a lack of capacity, which can be solved in this
case by adding one or more people I think.

Qemu is not a very large project in the grand scheme of things, and we
can hopefully avoid the kind of very cumbersome and heavyweight
processes which surround the Linux kernel.

Ian.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]