|
|
|
|
|
|
|
|
|
|
xen-devel
Re: [Xen-devel] [PATCH] Log qemu-dm's message with date, time and pid
On Tue, Jul 01, 2008 at 06:38:25PM +0100, Ian Jackson wrote:
> Daniel P. Berrange writes ("Re: [Xen-devel] [PATCH] Log qemu-dm's message
> with date, time and pid"):
> > What are your plans wrt to QEMU longer term ? Are you going to merge this
> > GIT repo into tools/ioemu in xen-unstable.hg, or thinking its better to
> > keep a separate tree on an ongoing basis ?
>
> No, I don't think it's practical to keep this tree in
> xen-unstable.hg. Everyone else doing work on qemu is using git (or
> svn).
That's the answer I was hoping for - I much prefer each component
to have its own source tree if the dependancies are clear-cut and
managable separately. Indeed in my ideal universe, every main component
under the tools/ directory in xen-unstable.hg would be independant!
> > Would we have synced up
> > releases of the two, or try to apply some ABI stability to libxc and
> > libxenstore APIs to allow separate release of QEMU vs XenD tools ?
>
> Releases of ioemu will follow releases of Xen, but commits will be
> made separately. So there will be at least some compatibility
> arrangements. I'm generally a fan of putting backward compatibility
> in interfaces, but I think for now we won't be making any promises.
Great, that sounds like a good way to move forward, improving the
maintainability of the QEMU / ioemu codebase.
Regards,
Daniel
--
|: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :|
|: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
|
|