From mboxrd@z Thu Jan 1 00:00:00 1970 From: Wei Liu Subject: Re: [PATCH] Config.mk: Update SEABIOS_UPSTREAM_TAG to rel-1.9.1 Date: Tue, 16 Feb 2016 13:52:28 +0000 Message-ID: <20160216135228.GP10489@citrix.com> References: <1455547082-6890-1-git-send-email-cardoe@cardoe.com> <20160215161354.GA11740@citrix.com> <1455630206.814.82.camel@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: Content-Disposition: inline In-Reply-To: <1455630206.814.82.camel@citrix.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 Campbell Cc: Keir Fraser , Tim Deegan , Doug Goldstein , xen-devel@lists.xen.org, Jan Beulich , Wei Liu , Ian Jackson List-Id: xen-devel@lists.xenproject.org On Tue, Feb 16, 2016 at 01:43:26PM +0000, Ian Campbell wrote: > On Mon, 2016-02-15 at 16:13 +0000, Wei Liu wrote: > > On Mon, Feb 15, 2016 at 08:38:02AM -0600, Doug Goldstein wrote: > > > Switch from tracking a commit post 1.9.0 to the 1.9.1 release. > > > = > > = > > Thanks for this patch. > > = > > We can't apply this patch just yet. We need to wait a bit until the > > change to upstream trickles down to our own tree [0] -- OSSTest will > > work on that shortly. See [1] for an example output. > = > Our osstest branch only tests seabios.git#master whereas this is tracking > the 1.9.x stable branch. > = > I don't think we really want/need the overhead of testing multiple branch= es > of SeaBIOS, so IMHO it is sufficient to observe that all of the commits on > the stable branch have passed our master branch commit gate (even if that > means they did so in the context of other un-backported patches). I haven= 't > checked but given the timings and=A0http://logs.test-lab.xenproject.org/o= sste > st/results/all-branch-statuses.txt=A0indicating our seabios branch is up = to > date I expect this is the case. > = > There is some risk to this, but SeaBIOS gets a fairly small number of > changes so the stable branches do not stray too far from master in general > so I think this approach is fine. > = > IOW it would be fine to push upstreams 1.9-stable to our repo along with > the rel-1.9.1 tag and to then apply this patch. > Makes sense.