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 2FD11200B7E for ; Tue, 23 Aug 2016 04:44:00 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 2E914160ABC; Tue, 23 Aug 2016 02:44:00 +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 6B89B160AB3 for ; Tue, 23 Aug 2016 04:43:59 +0200 (CEST) Received: (qmail 48991 invoked by uid 500); 23 Aug 2016 02:43:58 -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 48975 invoked by uid 99); 23 Aug 2016 02:43:58 -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, 23 Aug 2016 02:43:58 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 1DDF4DFCC0; Tue, 23 Aug 2016 02:43:58 +0000 (UTC) From: jburwell To: dev@cloudstack.apache.org Reply-To: dev@cloudstack.apache.org References: In-Reply-To: Subject: [GitHub] cloudstack issue #1646: [4.9/LTS] Add upgrade path from 4.9.0 to 4.9.1, chan... Content-Type: text/plain Message-Id: <20160823024358.1DDF4DFCC0@git1-us-west.apache.org> Date: Tue, 23 Aug 2016 02:43:58 +0000 (UTC) archived-at: Tue, 23 Aug 2016 02:44:00 -0000 Github user jburwell commented on the issue: https://github.com/apache/cloudstack/pull/1646 @rhtyd I understand the reasoning for two commits, and it makes sense. Since you understand the process required for the forward merge, I think it makes sense for you to perform it. LGTM for code. @karuturi @swill @wido are you able to provide a test LGTM? This PR is a blocker for cutting the 4.9.1.0 release candidate. --- 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. ---