From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JKxMP-0000Ag-73 for qemu-devel@nongnu.org; Fri, 01 Feb 2008 09:59:21 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JKxMM-00008x-Q3 for qemu-devel@nongnu.org; Fri, 01 Feb 2008 09:59:19 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JKxMM-00008u-K4 for qemu-devel@nongnu.org; Fri, 01 Feb 2008 09:59:18 -0500 Received: from rv-out-0910.google.com ([209.85.198.186]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JKxML-0006W7-79 for qemu-devel@nongnu.org; Fri, 01 Feb 2008 09:59:18 -0500 Received: by rv-out-0910.google.com with SMTP id g11so2423785rvb.22 for ; Fri, 01 Feb 2008 06:59:15 -0800 (PST) Message-ID: <47A333BB.3020901@codemonkey.ws> Date: Fri, 01 Feb 2008 08:59:07 -0600 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] Common Xen/KVM patchqueue repository? References: <20080201144744.GK4475@implementation.uk.xensource.com> In-Reply-To: <20080201144744.GK4475@implementation.uk.xensource.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Samuel Thibault wrote: > Hello, > Hi Samuel, > We were wondering whether it could be useful to have e.g. a git > repository holding the patches from Xen and KVM: while they are being > merged upstream, they could at least be shared by both projects... > KVM currently maintains a git tree of it's QEMU changes so unfortunately, things aren't nicely separated into patches. As you may have noticed, I've posted the core KVM support patches and I'm hoping we can merge them pretty soon. I am then going to follow up and try to get the remainder of the patches merged. In the short term, we will probably continue maintaining a git tree against QEMU as a staging repository but I hope that we can regularly sync up (just like we do with Linux). In the long term, I'd like KVM not to maintain a QEMU tree at all. In a broader sense, I know there are concerns about patches getting missed on qemu-devel. I don't think the solution is to maintain a separate patch queue, but to get the patches merged more quickly in the first place. Regards, Anthony Liguori > Samuel > > >