xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Doug Goldstein <cardoe@cardoe.com>
To: Wei Liu <wei.liu2@citrix.com>, Ian Campbell <ian.campbell@citrix.com>
Cc: Tim Deegan <tim@xen.org>, Keir Fraser <keir@xen.org>,
	Ian Jackson <ian.jackson@eu.citrix.com>,
	Jan Beulich <jbeulich@suse.com>,
	xen-devel@lists.xen.org
Subject: Re: [PATCH] Config.mk: Update SEABIOS_UPSTREAM_TAG to rel-1.9.1
Date: Wed, 24 Feb 2016 08:34:31 -0600	[thread overview]
Message-ID: <56CDBF77.2070103@cardoe.com> (raw)
In-Reply-To: <20160216135228.GP10489@citrix.com>


[-- Attachment #1.1: Type: text/plain, Size: 1558 bytes --]

On 2/16/16 7:52 AM, Wei Liu wrote:
> 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 branches
>> 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 http://logs.test-lab.xenproject.org/osste
>> st/results/all-branch-statuses.txt indicating 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.
> 

ping?

-- 
Doug Goldstein


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 959 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2016-02-24 14:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-15 14:38 [PATCH] Config.mk: Update SEABIOS_UPSTREAM_TAG to rel-1.9.1 Doug Goldstein
2016-02-15 16:13 ` Wei Liu
2016-02-16 13:43   ` Ian Campbell
2016-02-16 13:52     ` Wei Liu
2016-02-24 14:34       ` Doug Goldstein [this message]
2016-02-24 14:41         ` Wei Liu
2016-02-24 15:14           ` Jan Beulich
2016-02-24 15:18             ` Wei Liu
2016-02-24 15:44               ` Jan Beulich
2016-02-24 15:50                 ` Wei Liu
2016-02-26 19:02                   ` Konrad Rzeszutek Wilk

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=56CDBF77.2070103@cardoe.com \
    --to=cardoe@cardoe.com \
    --cc=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=jbeulich@suse.com \
    --cc=keir@xen.org \
    --cc=tim@xen.org \
    --cc=wei.liu2@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).