From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: Split kvm source tarballs Date: Wed, 25 Mar 2009 16:34:31 -0500 Message-ID: <49CAA367.9050404@codemonkey.ws> References: <49C64963.20601@redhat.com> <49CA2F16.1070905@codemonkey.ws> <49CA3058.3040600@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: KVM list To: Avi Kivity Return-path: Received: from qw-out-2122.google.com ([74.125.92.26]:55127 "EHLO qw-out-2122.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754751AbZCYVef (ORCPT ); Wed, 25 Mar 2009 17:34:35 -0400 Received: by qw-out-2122.google.com with SMTP id 8so279059qwh.37 for ; Wed, 25 Mar 2009 14:34:33 -0700 (PDT) In-Reply-To: <49CA3058.3040600@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: Hi Avi, I spent some time today putting together an approximation of the KVM stable release based on QEMU 0.10.x. In principle, it's not too bad at all because it's just a matter of creating a branch in kvm-userspace that's based a kvm commit sometime after the QEMU 0.10.x release but before the next qemu-cvs merge you did that happened post QEMU 0.10.x. Basically, it was a merge of 72ee81f and ddecccc. The problem for me is pulling in the QEMU stable fixes. You don't have a branch that tracks the QEMU stable tree and I can pull in the QEMU stable git tree without rewriting history since the directory layout is different. But if you created a qemu-svn-stable branch that followed the QEMU stable tree in kvm-userspace, like the qemu-cvs branch follows trunk, then it would be pretty easy to create and maintain a kvm_stable_0_10 branch of whatever you'd like to call it in kvm-userspace. Any chance you could do this? I suspect it's just a matter of creating the branch based off of the qemu-cvs tree at ddecccc and then doing a git-svn fetch. Regards, Anthony Liguori