Avi, Should libc and a kernel be put into the same repository? As far as I have seen, the pain of migrating kvm into git was caused by interface incompatibility between libkvm and kvm due to rapid interface flux. I think the interface should be well-defined, and boiled down, to the point that libkvm as a userspace component could be replaced by another userspace program without kvm noticing (and vice versa). I think this implies that integration between libkvm and kvm repositories is unnecessary and possibly hindering potential stability.
As you suggest, storing a git reference to kvm along with libkvm subversion code would be very handy during periods of rapid interface development, in order to synchronize from libkvm to kvm, momentarily. One might also create a subversion tag in libkvm repository that matches a git reference or tag, to synchronize from kvm to libkvm. Ultimately, hammering out a written interface specification that keys on kernel version numbers might work. David Beal On Tue, Mar 20, 2007 at 02:13:11PM +0200, 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. ------------------------------------------------------------------------- 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 _______________________________________________ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
