All of lore.kernel.org
 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: Re: [GIT-PULL OSSTEST] ap-fetch-version: Arrange for osstest merges from upstream to be stable
Date: Tue, 14 Jul 2015 09:27:41 +0100	[thread overview]
Message-ID: <1436862461.25044.23.camel@citrix.com> (raw)
In-Reply-To: <21923.61275.147451.722661@mariner.uk.xensource.com>

On Mon, 2015-07-13 at 18:03 +0100, Ian Jackson wrote:
> Ian Campbell writes ("[GIT-PULL OSSTEST] ap-fetch-version: Arrange for osstest merges from upstream to be stable"):
> > "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.
> 
> I have merged, and pushed this to pretest in the colo.

Thanks.

> Let us avoid pushing anything else to pretest for a bit, so that we
> can contain the history mess.

The Cambridge instance is currently stopped. I won't unstop it until
this merge passes mainline pretest, at which point further merges into
Cambridge should be fast forwarding again.

Ian.

      reply	other threads:[~2015-07-14  8:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-13  8:19 [GIT-PULL OSSTEST] ap-fetch-version: Arrange for osstest merges from upstream to be stable Ian Campbell
2015-07-13 17:03 ` Ian Jackson
2015-07-14  8:27   ` 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=1436862461.25044.23.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 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.