From: Ian Campbell <ian.campbell@citrix.com>
To: "Hao, Xudong" <xudong.hao@intel.com>
Cc: "andrew.cooper3@citrix.com" <andrew.cooper3@citrix.com>,
Jan Beulich <JBeulich@suse.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Does Xen unstable tree work?
Date: Tue, 12 May 2015 09:22:40 +0100 [thread overview]
Message-ID: <1431418960.16382.44.camel@citrix.com> (raw)
In-Reply-To: <B8376D2DEA074F45BA033984477C453EB14610@shsmsx102.ccr.corp.intel.com>
On Tue, 2015-05-12 at 00:47 +0000, Hao, Xudong wrote:
> Xen unstable tree doesn't update for about one month, I saw staging
> tree has many new commit these days, how often does it merging? Does
> unstable tree still work?
There have been some teething troubles with the push gates since osstest
moved to the new hosting facility, causing spurious failures and other
throughput issues, so staging is lagging behind master fairly
significantly at the moment.
This seem to be back on track (knock on wood) and I hope we will get a
pass in the next day or so (I expect either tonight or early morning UK
time).
Ian.
prev parent reply other threads:[~2015-05-12 8:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-12 0:47 Does Xen unstable tree work? Hao, Xudong
2015-05-12 8:22 ` Ian Campbell [this message]
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=1431418960.16382.44.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=xen-devel@lists.xen.org \
--cc=xudong.hao@intel.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.