From mboxrd@z Thu Jan  1 00:00:00 1970
From: konrad wilk <konrad.wilk@oracle.com>
Subject: Re: [PATCH for-xen-4.5 v4 00/18] xen: Break multiboot
 (v1) dependency and add multiboot2 support
Date: Thu, 23 Oct 2014 14:04:51 -0400
Message-ID: <54494343.3030502@oracle.com>
References: <1413555132-22138-1-git-send-email-daniel.kiper@oracle.com>
	<544146FE020000780003FA95@mail.emea.novell.com>
	<20141017154936.GE3467@olila.local.net-space.pl>
	<5448F24D02000078000415FE@mail.emea.novell.com>
	<5448E1B0.6050301@citrix.com>
	<20141023145745.GP3467@olila.local.net-space.pl>
	<544924D6.1030601@citrix.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <konrad.wilk@oracle.com>) id 1XhMpy-0003va-MW
	for xen-devel@lists.xenproject.org; Thu, 23 Oct 2014 18:10:14 +0000
In-Reply-To: <544924D6.1030601@citrix.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Juergen Gross <JGross@suse.com>, keir@xen.org, ian.campbell@citrix.com, stefano.stabellini@eu.citrix.com, Daniel Kiper <daniel.kiper@oracle.com>, ross.philipson@citrix.com, roy.franz@linaro.org, ning.sun@intel.com, Jan Beulich <JBeulich@suse.com>, xen-devel@lists.xenproject.org, qiaowei.ren@intel.com, richard.l.maliszewski@intel.com, gang.wei@intel.com, fu.wei@linaro.org
List-Id: xen-devel@lists.xenproject.org


> Furthermore, there is still an open question of whether "unify all boot
> paths" is indeed a clever idea in the first place.  Again, this is
> ideally something which should have been argued over / decided upon as
> part of the design review.  (People on the list might notice a
> reoccurring theme there, when it comes to doing large chunks of work.)
>

And it _was_ discussed at the Xen hackathon multiple times - where it 
seems it was the perfect place to hash this out.

Or are we saying that any big project in Xen MUST have a design document 
with it? If so we really need to document that somewhere.

This is frustrating.