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 A3E68200BD3 for ; Tue, 6 Dec 2016 20:21:37 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id A2763160B1B; Tue, 6 Dec 2016 19:21:37 +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 E3F5B160B17 for ; Tue, 6 Dec 2016 20:21:36 +0100 (CET) Received: (qmail 74404 invoked by uid 500); 6 Dec 2016 19:21:36 -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 74393 invoked by uid 99); 6 Dec 2016 19:21:35 -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, 06 Dec 2016 19:21:35 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id A0415E0159; Tue, 6 Dec 2016 19:21:35 +0000 (UTC) From: rhtyd To: dev@cloudstack.apache.org Reply-To: dev@cloudstack.apache.org References: In-Reply-To: Subject: [GitHub] cloudstack issue #1807: CLOUDSTACK-9633: Revert addition of `vhd` extention ... Content-Type: text/plain Message-Id: <20161206192135.A0415E0159@git1-us-west.apache.org> Date: Tue, 6 Dec 2016 19:21:35 +0000 (UTC) archived-at: Tue, 06 Dec 2016 19:21:37 -0000 Github user rhtyd commented on the issue: https://github.com/apache/cloudstack/pull/1807 @serg38 I think we can do that, but will be also need some tooling to rename the actual files on the SRs? /cc @abhinandanprateek --- 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. ---