From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: Split kvm source tarballs Date: Thu, 26 Mar 2009 11:09:07 +0200 Message-ID: <49CB4633.5020208@redhat.com> References: <49C64963.20601@redhat.com> <49CA2F16.1070905@codemonkey.ws> <49CA3058.3040600@redhat.com> <49CA355A.6010803@codemonkey.ws> <20090325164707.GA16225@infradead.org> <49CA71C8.3000407@redhat.com> <20090325181716.GA3215@infradead.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Anthony Liguori , KVM list To: Christoph Hellwig Return-path: Received: from mx2.redhat.com ([66.187.237.31]:36531 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757765AbZCZJJY (ORCPT ); Thu, 26 Mar 2009 05:09:24 -0400 In-Reply-To: <20090325181716.GA3215@infradead.org> Sender: kvm-owner@vger.kernel.org List-ID: Christoph Hellwig wrote: >> - move qemu to the root of the repository, and reparent libkvm/ user/ >> and friends under it. this will give us easier merging. >> > > Yeah. While you're at it user/ might be renamed to something more > descriptive. > The subdirectory test/ under it can be ported to run under qemu and contributed into qemu's test suite. >> - move the external module kit into kvm.git >> > > As in your kvm development kernel tree? Not sure it's a good idea > to suck this into a full kernel tree. Probably worth making it a small > repository of it's own. > If the repo contains only the kit (external-module.h and the hack scripts) we'll be left with dual repositories with their confusion and unbisectability. If the repo contains both the kit and the code, I'll need to commit every kvm.git change into that repository, which I'm sure to botch now and then. Do you see any specific problem with dropping kvm-userspace.git/kernel/* under kvm.git/scripts/kvm/? -- error compiling committee.c: too many arguments to function