From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ian Jackson <Ian.Jackson@eu.citrix.com>
Subject: Re: [PATCH] Config.mk: update OVMF changeset
Date: Thu, 22 Oct 2015 18:08:41 +0100
Message-ID: <22057.6169.341549.297357@mariner.uk.xensource.com>
References: <1444822873-28287-1-git-send-email-wei.liu2@citrix.com>
	<1445529318.2374.29.camel@citrix.com>
	<22057.1980.705627.525934@mariner.uk.xensource.com>
	<1445530173.2374.41.camel@citrix.com>
	<alpine.DEB.2.02.1510221711090.15801@kaball.uk.xensource.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <prvs=7304e4abf=Ian.Jackson@citrix.com>)
	id 1ZpJM8-00071x-Oa
	for xen-devel@lists.xenproject.org; Thu, 22 Oct 2015 17:08:48 +0000
In-Reply-To: <alpine.DEB.2.02.1510221711090.15801@kaball.uk.xensource.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: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Xen-devel <xen-devel@lists.xenproject.org>, Wei Liu <wei.liu2@citrix.com>, Ian Campbell <ian.campbell@citrix.com>, Jan Beulich <JBeulich@suse.com>
List-Id: xen-devel@lists.xenproject.org

Stefano Stabellini writes ("Re: [PATCH] Config.mk: update OVMF changeset"):
> On Thu, 22 Oct 2015, Ian Campbell wrote:
> > This was discussed prior to Wei submitting this patch, but I can't remember
> > the reference. Hopefully either Wei or Stefano does.
> 
> 1444832748.23192.213.camel@citrix.com

Thanks for the reference.

I'm quite uncomfortable with this, really.

People who are using xen.git stable branches ought to get only changes
that we (or perhaps, someone else whose judgement we have some reason
to trust) have intentionally decided are suitable for deployment as a
bugfix or security update in an existing installation.

Ie, changes in stable branches are supposed to be low risk.  That's
not compatible with tracking an upstream development branch.

Sorry,
Ian.