xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel <xen-devel@lists.xen.org>
Subject: [GIT-PULL OSSTEST] ap-fetch-version: Arrange for osstest merges from upstream to be stable
Date: Mon, 13 Jul 2015 09:19:26 +0100	[thread overview]
Message-ID: <1436775566.7019.20.camel@citrix.com> (raw)

"ap-fetch-version: Arrange for osstest merges from upstream to be
stable" has now passed the Cambridge push gate and done a couple of
merges from upstream as well as some failed attempts, which behaved as
expected. I've dropped a stop file in Cambridge while this pull request
is pending, so we don't end up racing.

The following changes since commit 11e788f7b180ff7e693f7342617318ff01c961c5:

  JobDB/Executive: Improve an internal `die' error (2015-07-09 12:47:38 +0100)

are available in the git repository at:

  git://xenbits.xen.org/people/ianc/osstest.git from-cambridge/2015-07-13

for you to fetch changes up to 43b59cba103da97fd15ab63f570706a1b149970f:

  Automerge of git://xenbits.xen.org/osstest.git master into production (2015-07-11 08:35:43 +0100)

----------------------------------------------------------------
Ian Campbell (1):
      ap-fetch-version: Arrange for osstest merges from upstream to be stable

xen.org (2):
      Automerge of git://xenbits.xen.org/osstest.git master into production
      Automerge of git://xenbits.xen.org/osstest.git master into production

 ap-fetch-version | 36 +++++++++++++++++++++++++++++++++---
 1 file changed, 33 insertions(+), 3 deletions(-)

             reply	other threads:[~2015-07-13  8:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-13  8:19 Ian Campbell [this message]
2015-07-13 17:03 ` [GIT-PULL OSSTEST] ap-fetch-version: Arrange for osstest merges from upstream to be stable Ian Jackson
2015-07-14  8:27   ` 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=1436775566.7019.20.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=Ian.Jackson@eu.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).