From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: [OSSTEST PATCH 06/10] Flight restriction: Change implementation of --max-flight Date: Fri, 24 Jul 2015 10:24:39 +0100 Message-ID: <1437729879.24746.49.camel@citrix.com> References: <1437675564-16602-1-git-send-email-ian.jackson@eu.citrix.com> <1437675564-16602-7-git-send-email-ian.jackson@eu.citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1ZIZDg-0003Jl-Iw for xen-devel@lists.xenproject.org; Fri, 24 Jul 2015 09:24:44 +0000 In-Reply-To: <1437675564-16602-7-git-send-email-ian.jackson@eu.citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Jackson , xen-devel@lists.xenproject.org List-Id: xen-devel@lists.xenproject.org On Thu, 2015-07-23 at 19:19 +0100, Ian Jackson wrote: > Abolish $maxflight. All the users outside Osstest::Executive have > been eliminated, so this is fine. Replace it with > $restrictflight_cond, which can accumulate multiple conditions. > > There is a minor functional change: when multiple --max-flight > options > are specified, _all_ of them take effect (effectively using the > lowest > value). That option is not used in production, and I don't expect > people elsewhere to be passing multiple different such options. > > Signed-off-by: Ian Jackson Acked-by: Ian Campbell