From: "Daniel P. Berrange" <berrange@redhat.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: Yuji Shimada <shimada-yxb@necst.nec.co.jp>,
xen-devel@lists.xensource.com,
Yosuke Iwamatsu <y-iwamatsu@ab.jp.nec.com>,
Kevin Wolf <kwolf@suse.de>
Subject: Re: [PATCH] Log qemu-dm's message with date, time and pid
Date: Tue, 1 Jul 2008 19:10:46 +0100 [thread overview]
Message-ID: <20080701181046.GA25624@redhat.com> (raw)
In-Reply-To: <18538.27537.718044.726790@mariner.uk.xensource.com>
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 :|
next prev parent reply other threads:[~2008-07-01 18:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-26 5:02 [PATCH] Log qemu-dm's message with date, time and pid Yosuke Iwamatsu
2008-06-26 11:20 ` Kevin Wolf
2008-06-26 14:46 ` Ian Jackson
2008-06-26 16:38 ` Daniel P. Berrange
2008-07-01 17:38 ` Ian Jackson
2008-07-01 18:10 ` Daniel P. Berrange [this message]
2008-07-01 20:06 ` John Levon
2008-07-02 10:26 ` Ian Jackson
2008-07-02 10:41 ` Daniel P. Berrange
2008-07-02 15:20 ` Brendan Cully
2008-06-27 8:19 ` Yuji Shimada
2008-06-27 9:10 ` Kevin Wolf
2008-06-27 13:40 ` Ian Jackson
2008-06-30 8:21 ` Yuji Shimada
2008-06-30 9:45 ` Kevin Wolf
2008-07-01 8:01 ` Yuji Shimada
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080701181046.GA25624@redhat.com \
--to=berrange@redhat.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=kwolf@suse.de \
--cc=shimada-yxb@necst.nec.co.jp \
--cc=xen-devel@lists.xensource.com \
--cc=y-iwamatsu@ab.jp.nec.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.