From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [Qemu-devel] Planning for the 0.11.0 release Date: Sun, 12 Jul 2009 11:31:24 +0300 Message-ID: <4A599F5C.8040009@redhat.com> References: <4A401A65.3080804@us.ibm.com> <1247128021.22231.1.camel@blaa> <4A55F150.3020803@codemonkey.ws> <87eisp1gx2.fsf@pike.pond.sub.org> <4A5747E4.3030101@us.ibm.com> <4A57586B.9050900@siemens.com> <4A576317.6010000@us.ibm.com> <4A577291.4000206@redhat.com> <4A57751E.3070005@us.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Kevin Wolf , "qemu-devel@nongnu.org" , kvm-devel To: Anthony Liguori Return-path: Received: from mx2.redhat.com ([66.187.237.31]:60098 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751058AbZGLI2d (ORCPT ); Sun, 12 Jul 2009 04:28:33 -0400 In-Reply-To: <4A57751E.3070005@us.ibm.com> Sender: kvm-owner@vger.kernel.org List-ID: On 07/10/2009 08:06 PM, Anthony Liguori wrote: > BTW, this is one of the challenges of doing pulls. I did the pull and > then deleted every qemu-io patch in my queue since I assumed that > everything that should go in was part of hch's pull request. In > general, that's the only sane way to do pulls so if someone requests a > pull in the future, please make sure that you've gone through and > pulled any patch from the list first. Pulls and stale queues are incompatible. So long as everything is in patches, it doesn't matter since duplicate patches won't apply. However a branch can't be based on a queue (since that's liable to change any time), and the branch can't commit and patches in the queue (since the queue might be committed any time). If you want to pull, you'll need to shorten your queues (that will improve many other people's quality of life, btw). -- error compiling committee.c: too many arguments to function