From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: [PATCH 4/9] raisin: add a component to build qemu_traditional Date: Wed, 15 Apr 2015 17:26:26 +0100 Message-ID: <1429115186.25195.9.camel@citrix.com> References: <1429110900-8286-4-git-send-email-stefano.stabellini@eu.citrix.com> <552E832A.9020900@citrix.com> <552E8870.6020302@citrix.com> <1429113529.15516.344.camel@citrix.com> <21806.36527.622876.472825@mariner.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <21806.36527.622876.472825@mariner.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Jackson Cc: george.dunlap@eu.citrix.com, Andrew Cooper , xen-devel@lists.xensource.com, Stefano Stabellini List-Id: xen-devel@lists.xenproject.org On Wed, 2015-04-15 at 17:15 +0100, Ian Jackson wrote: > Stefano Stabellini writes ("Re: [Xen-devel] [PATCH 4/9] raisin: add a component to build qemu_traditional"): > > On Wed, 15 Apr 2015, Ian Campbell wrote: > > > (I also think osstest support is a prerequisite for saying it is an > > > officially support XenProject thing, but that's offtopic in this > > > context) > > > > I spoke with IanJ and he didn't seem too keen on adding raisin support > > to osstest before raisin could build everything out of tree. That's way > > I started tackling qemu and qemu-traditional. I see, I had imagined we would prefer a more piecemeal process. > I don't mind a hybrid approach. What I would like is for each > subproject to _either_ do the existing thing, or be able to ask raisin > about it in advance. Isn't that going to be useful/necessary anyway? e.g. as new (i.e. completely new, not moving from xen.git) stuff is added and desirable to support. Ian.