From: George Dunlap <george.dunlap@eu.citrix.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Ian Campbell <Ian.Campbell@citrix.com>
Cc: Anthony Perard <anthony.perard@citrix.com>,
Stefano Stabellini <stefano.stabellini@citrix.com>,
xen-devel@lists.xensource.com,
"xen.org" <ian.jackson@eu.citrix.com>
Subject: Re: [qemu-upstream-unstable test] 24553: tolerable FAIL - PUSHED
Date: Tue, 28 Jan 2014 14:30:47 +0000 [thread overview]
Message-ID: <52E7BF17.3050200@eu.citrix.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1401281228100.4373@kaball.uk.xensource.com>
On 01/28/2014 12:29 PM, Stefano Stabellini wrote:
> On Tue, 28 Jan 2014, Ian Campbell wrote:
>> On Tue, 2014-01-28 at 02:16 +0000, xen.org wrote:
>>> flight 24553 qemu-upstream-unstable real [real]
>>> http://www.chiark.greenend.org.uk/~xensrcts/logs/24553/
>>>
>>> Failures :-/ but no regressions.
>>
>> QEMU_UPSTREAM_REVISION in xen.git is currently set to qemu-xen-4.4.0-rc1
>> and so will require updating to actually pull this new stuff into the
>> release.
>
> OK. But given that the new code is not part of any RCs, should I wait
> for the next one? Should we go back to "master"?
I guess we should have gone back to "master" after tagging the last RC?
-George
next prev parent reply other threads:[~2014-01-28 14:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-28 2:16 [qemu-upstream-unstable test] 24553: tolerable FAIL - PUSHED xen.org
2014-01-28 9:37 ` Ian Campbell
2014-01-28 12:29 ` Stefano Stabellini
2014-01-28 14:30 ` George Dunlap [this message]
2014-01-28 14:32 ` Stefano Stabellini
2014-01-28 15:08 ` Jan Beulich
2014-01-28 15:24 ` Stefano Stabellini
2014-01-28 15:31 ` Ian Campbell
2014-01-28 15:33 ` Stefano Stabellini
2014-01-28 15:36 ` Ian Campbell
2014-01-28 15:48 ` Jan Beulich
2014-01-28 15:37 ` Jan Beulich
2014-01-28 15:42 ` Ian Campbell
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=52E7BF17.3050200@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=anthony.perard@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=stefano.stabellini@citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.