Return-Path: X-Original-To: apmail-cloudstack-dev-archive@www.apache.org Delivered-To: apmail-cloudstack-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id DB57A102FC for ; Sat, 24 Oct 2015 17:45:01 +0000 (UTC) Received: (qmail 78006 invoked by uid 500); 24 Oct 2015 17:45:01 -0000 Delivered-To: apmail-cloudstack-dev-archive@cloudstack.apache.org Received: (qmail 77949 invoked by uid 500); 24 Oct 2015 17:45: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 77938 invoked by uid 99); 24 Oct 2015 17:45: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; Sat, 24 Oct 2015 17:45:01 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id C3364DFFC2; Sat, 24 Oct 2015 17:45:00 +0000 (UTC) From: remibergsma To: dev@cloudstack.apache.org Reply-To: dev@cloudstack.apache.org References: In-Reply-To: Subject: [GitHub] cloudstack pull request: Fix for CLOUDSTACK-8937 - XenServer migra... Content-Type: text/plain Message-Id: <20151024174500.C3364DFFC2@git1-us-west.apache.org> Date: Sat, 24 Oct 2015 17:45:00 +0000 (UTC) Github user remibergsma commented on the pull request: https://github.com/apache/cloudstack/pull/925#issuecomment-150836810 Hi @atrbgithub Thanks for your response. We indeed need to reimplement your fix on current master. Once that is in place and tested, we merge it on master (that will soon become 4.6.0). Then we can merge this PR (with the same functionality) to 4.5 and it will be in 4.5.3. It cannot go into 4.5.3 before it is also in master. Let me know if you need help! --- 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. ---