All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Jackson <ian.jackson@eu.citrix.com>
To: Anthony PERARD <anthony.perard@citrix.com>
Cc: xen-devel@lists.xen.org
Subject: Re: [OSSTEST PATCH v9 1/3] ts-openstack-deploy: Deploy OpenStack on a host with devstack
Date: Fri, 7 Apr 2017 11:35:42 +0100	[thread overview]
Message-ID: <22759.27518.235734.801965@mariner.uk.xensource.com> (raw)
In-Reply-To: <20170407103212.GF1710@perard.uk.xensource.com>

Anthony PERARD writes ("Re: [OSSTEST PATCH v9 1/3] ts-openstack-deploy: Deploy OpenStack on a host with devstack"):
> On Thu, Apr 06, 2017 at 05:32:32PM +0100, Ian Jackson wrote:
> > Also, it would be worth grepping for other occurrences of target_cmd
> > with missing set -e.  (target_cmd_build implies set -e.)
> > 
> > Would that be OK ?
> 
> Yes, that's OK. I'll add the `set -e`s in my branch.

Thanks.

> I guess 'target_cmd_root' needs the same treatment.

Indeed.

Thanks,
Ian.

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

  reply	other threads:[~2017-04-07 10:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-13 18:10 [OSSTEST PATCH v9 0/3] Have OpenStack tested on top of xen's master and libvirt's master Anthony PERARD
2016-12-13 18:10 ` [OSSTEST PATCH v9 1/3] ts-openstack-deploy: Deploy OpenStack on a host with devstack Anthony PERARD
2017-04-06 16:32   ` Ian Jackson
2017-04-07 10:32     ` Anthony PERARD
2017-04-07 10:35       ` Ian Jackson [this message]
2016-12-13 18:10 ` [OSSTEST PATCH v9 2/3] ts-openstack-tempest: Run Tempest to check OpenStack Anthony PERARD
2016-12-13 18:10 ` [OSSTEST PATCH v9 3/3] Create a flight to test OpenStack with xen-unstable and libvirt Anthony PERARD
2016-12-13 18:25   ` Ian Jackson
2017-01-13 19:38     ` Ian Jackson
2017-01-16 11:27       ` Anthony PERARD
2017-01-16 14:55         ` Ian Jackson

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=22759.27518.235734.801965@mariner.uk.xensource.com \
    --to=ian.jackson@eu.citrix.com \
    --cc=anthony.perard@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.