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 0BB47200BCE for ; Fri, 2 Dec 2016 09:53:03 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 0A600160B24; Fri, 2 Dec 2016 08:53:03 +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 4F725160B16 for ; Fri, 2 Dec 2016 09:53:02 +0100 (CET) Received: (qmail 14424 invoked by uid 500); 2 Dec 2016 08:53:01 -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 14412 invoked by uid 99); 2 Dec 2016 08:53:01 -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; Fri, 02 Dec 2016 08:53:01 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 0E12DE055E; Fri, 2 Dec 2016 08:53:01 +0000 (UTC) From: rhtyd To: dev@cloudstack.apache.org Reply-To: dev@cloudstack.apache.org References: In-Reply-To: Subject: [GitHub] cloudstack issue #1257: CLOUDSTACK-9175: [VMware DRS] Adding new host to DRS... Content-Type: text/plain Message-Id: <20161202085301.0E12DE055E@git1-us-west.apache.org> Date: Fri, 2 Dec 2016 08:53:01 +0000 (UTC) archived-at: Fri, 02 Dec 2016 08:53:03 -0000 Github user rhtyd commented on the issue: https://github.com/apache/cloudstack/pull/1257 @sureshanaparti do you think this would be useful for 4.9? If so, can you change PR's base branch to 4.9 and rebase your branch against 4.9? --- 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. ---