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 BE96D200A01 for ; Tue, 3 May 2016 18:06:53 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id BE2081609F4; Tue, 3 May 2016 18:06:53 +0200 (CEST) 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 0B71D1609A9 for ; Tue, 3 May 2016 18:06:52 +0200 (CEST) Received: (qmail 38380 invoked by uid 500); 3 May 2016 16:06:51 -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 38369 invoked by uid 99); 3 May 2016 16:06:51 -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; Tue, 03 May 2016 16:06:51 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 34892DFC77; Tue, 3 May 2016 16:06:51 +0000 (UTC) From: swill To: dev@cloudstack.apache.org Reply-To: dev@cloudstack.apache.org References: In-Reply-To: Subject: [GitHub] cloudstack pull request: Set default networkDomain to empty instea... Content-Type: text/plain Message-Id: <20160503160651.34892DFC77@git1-us-west.apache.org> Date: Tue, 3 May 2016 16:06:51 +0000 (UTC) archived-at: Tue, 03 May 2016 16:06:53 -0000 Github user swill commented on the pull request: https://github.com/apache/cloudstack/pull/1485#issuecomment-216578573 My CI does not have the capability of testing this, so even if I ran CI it would not cover this. I tend to agree that his is fine as is. --- 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. ---