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 200D3200C15 for ; Wed, 8 Feb 2017 07:57:56 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 1E89D160B5A; Wed, 8 Feb 2017 06:57:56 +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 5BF4F160B4E for ; Wed, 8 Feb 2017 07:57:55 +0100 (CET) Received: (qmail 24028 invoked by uid 500); 8 Feb 2017 06:57:54 -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 24017 invoked by uid 99); 8 Feb 2017 06:57:54 -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; Wed, 08 Feb 2017 06:57:54 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id B90F5DFBDB; Wed, 8 Feb 2017 06:57:53 +0000 (UTC) From: karuturi To: dev@cloudstack.apache.org Reply-To: dev@cloudstack.apache.org References: In-Reply-To: Subject: [GitHub] cloudstack issue #1905: CLOUDSTACK-9738: [Vmware] Optimize vm expunge proces... Content-Type: text/plain Message-Id: <20170208065753.B90F5DFBDB@git1-us-west.apache.org> Date: Wed, 8 Feb 2017 06:57:53 +0000 (UTC) archived-at: Wed, 08 Feb 2017 06:57:56 -0000 Github user karuturi commented on the issue: https://github.com/apache/cloudstack/pull/1905 Thanks for the clarification. Its a nice enhancement. LGTM for the changes. Marvin tests are always welcome :) --- 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. ---