From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Gregory Haskins" Subject: Re: kvm repository unification Date: Tue, 20 Mar 2007 08:58:11 -0400 Message-ID: <45FF9418.BA47.005A.0@novell.com> References: <45FFCFD7.5000107@qumranet.com> <45FF8B73.BA47.005A.0@novell.com> <45FFD598.2050403@qumranet.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel To: "Avi Kivity" Return-path: In-Reply-To: <45FFD598.2050403-atKUWr5tajBWk0Htik3J/w@public.gmane.org> Content-Disposition: inline List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: kvm.vger.kernel.org >>> On Tue, Mar 20, 2007 at 8:37 AM, in message <45FFD598.2050403-atKUWr5tajBWk0Htik3J/w@public.gmane.org>, Avi Kivity wrote: > Gregory Haskins wrote: >> Avi Kivity wrote: >> >>> Managing userspace in subversion and the kernel in git is proving to be >>> quite a pain. Branches have to be maintained in parallel, tagging is >>> awkward, and bisection is fairly impossible. >>> >>> What do people think about putting libkvm and qemu into the usr >>> directory of the kernel repo? It's slightly wierd but will make life >>> generally easier. >>> >> >> >> That does sounds a little weird, though I know what you mean about managing > the two disparate repos. I think having one repo makes sense, but I dont > know if putting that in the kernel tree is the right direction. Is there > another way? For instance, go back to using /kernel, /libkvm, and /qemu from > SVN and submitting patches/drops to the kernel tree. I am not advocating SVN > over GIT either...the new unified repo could be whatever. I think the most > important thing is having it in one place. >> > > With the paravirt stuff we are placing things all over the kernel, and > tighter integration with the scheduler and mm infrastructure will make > having a kernel/ directory impossible. > Thats a good point. Note that having things sprinkled all over the kernel verses contained in one place (e.g. /drivers/kvm) doesnt preclude this model that I suggested per se. But perhaps that is too messy to deal with. I think getting them in one repo is more important than which repo. So if you can make the integration with the kernel tree work from a political standpoint, I'd say go for it. -Greg ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV