From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: Ian Campbell <ian.campbell@citrix.com>
Cc: Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Jan Beulich <JBeulich@suse.com>,
xen-devel <xen-devel@lists.xen.org>
Subject: Re: [RFC for-4.7] Switching to a single qemu tree each per qemu-xen and qemu-trad
Date: Thu, 30 Jul 2015 16:51:00 +0200 [thread overview]
Message-ID: <87twslaecr.fsf@vitty.brq.redhat.com> (raw)
In-Reply-To: <1438266156.11600.347.camel@citrix.com> (Ian Campbell's message of "Thu, 30 Jul 2015 15:22:36 +0100")
Ian Campbell <ian.campbell@citrix.com> writes:
> (CC-ing 2x QEMU maintainers and stable release manager)
>
> The separate trees are a holdover from mercurial, which didn't (at the
> time) have a good in-repo branching model.
>
> I propose that Xen 4.6 should be the last release which uses these split
> trees and that instead we combine them into just qemu-xen.git (upstream)
> and qemu-xen-traditional.git (our old fork)
(sorry my question is a bit unrelated)
is there a proposed time frame for the retirement of
qemu-xen-traditional? http://wiki.xenproject.org/wiki/QEMU_Upstream only
mentions VGA passthrough as a missing feature but maybe it can be fixed
for 4.7?
--
Vitaly
next prev parent reply other threads:[~2015-07-30 14:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-30 14:22 [RFC for-4.7] Switching to a single qemu tree each per qemu-xen and qemu-trad Ian Campbell
2015-07-30 14:33 ` Ian Jackson
2015-07-30 14:46 ` Ian Campbell
2015-07-30 14:40 ` Andrew Cooper
2015-07-30 15:11 ` Ian Jackson
2015-07-30 14:51 ` Vitaly Kuznetsov [this message]
2015-07-30 14:57 ` Ian Campbell
2015-08-03 10:14 ` George Dunlap
2015-08-11 14:45 ` Jan Beulich
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=87twslaecr.fsf@vitty.brq.redhat.com \
--to=vkuznets@redhat.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=ian.campbell@citrix.com \
--cc=xen-devel@lists.xen.org \
/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.