Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 8D546200BCA for ; Mon, 21 Nov 2016 08:55:08 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 8C98A160AEC; Mon, 21 Nov 2016 07:55:08 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id CE2FA160AF9 for ; Mon, 21 Nov 2016 08:55:07 +0100 (CET) Received: (qmail 23543 invoked by uid 500); 21 Nov 2016 07:55:06 -0000 Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list dev@cloudstack.apache.org Received: (qmail 22926 invoked by uid 99); 21 Nov 2016 07:55:06 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 21 Nov 2016 07:55:06 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 66F1AE0999; Mon, 21 Nov 2016 07:55:06 +0000 (UTC) From: blueorangutan To: dev@cloudstack.apache.org Reply-To: dev@cloudstack.apache.org References: In-Reply-To: Subject: [GitHub] cloudstack issue #1681: CLOUDSTACK-9491: incorrect parsing of device list to... Content-Type: text/plain Message-Id: <20161121075506.66F1AE0999@git1-us-west.apache.org> Date: Mon, 21 Nov 2016 07:55:06 +0000 (UTC) archived-at: Mon, 21 Nov 2016 07:55:08 -0000 Github user blueorangutan commented on the issue: https://github.com/apache/cloudstack/pull/1681 @rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastructure@apache.org or file a JIRA ticket with INFRA. ---