From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MQps4-0006jD-A3 for qemu-devel@nongnu.org; Tue, 14 Jul 2009 17:49:08 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MQprz-0006Wm-BY for qemu-devel@nongnu.org; Tue, 14 Jul 2009 17:49:07 -0400 Received: from [199.232.76.173] (port=52211 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MQprz-0006WK-8D for qemu-devel@nongnu.org; Tue, 14 Jul 2009 17:49:03 -0400 Received: from mx2.redhat.com ([66.187.237.31]:56758) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MQpry-0007M8-Kj for qemu-devel@nongnu.org; Tue, 14 Jul 2009 17:49:02 -0400 Message-ID: <4A5CFD47.7050803@redhat.com> Date: Tue, 14 Jul 2009 23:48:55 +0200 From: Gerd Hoffmann MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] qdev merge plans? List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: aliguori@codemonkey.ws Cc: "qemu-devel@nongnu.org" Hi Anthony, Your queue continues bitrotting. BlueSwirl did more qdev conversions with the result that more fixups are needed to make the tree build again once your queue is pushed ... For now I did incremental fixups and didn't change the patches you have queued up already. At least for the build failure this isn't ideal though as it leaves a few revisions which don't build which is bad for bisecting. So what is your plan to handle the mess^H^H^H^Hmerge? I plan to respin my patches tomorrow and can adjust the patches the way you want to have it. cheers, Gerd PS: complete patch queue (including work-in-progress bits) is at http://git.et.redhat.com/?p=qemu-kraxel.git;a=shortlog;h=refs/heads/qdev.v11