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 72D67200BD0 for ; Wed, 30 Nov 2016 21:32:53 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 7187A160B13; Wed, 30 Nov 2016 20:32:53 +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 AF091160B06 for ; Wed, 30 Nov 2016 21:32:52 +0100 (CET) Received: (qmail 51010 invoked by uid 500); 30 Nov 2016 20:32:51 -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 50999 invoked by uid 99); 30 Nov 2016 20:32:51 -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, 30 Nov 2016 20:32:51 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 4EF85DFCF8; Wed, 30 Nov 2016 20:32:51 +0000 (UTC) From: pdion891 To: dev@cloudstack.apache.org Reply-To: dev@cloudstack.apache.org References: In-Reply-To: Subject: [GitHub] cloudstack issue #1769: tools: fix Dockerfile Content-Type: text/plain Message-Id: <20161130203251.4EF85DFCF8@git1-us-west.apache.org> Date: Wed, 30 Nov 2016 20:32:51 +0000 (UTC) archived-at: Wed, 30 Nov 2016 20:32:53 -0000 Github user pdion891 commented on the issue: https://github.com/apache/cloudstack/pull/1769 So, should we go forward and merge #1435 + #1769 to master? I might just need to rebase and update version number of the current commit. With those 2 PR, we would have master back online on dockerhub so we can get an updater docker image for the simulator! --- 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. ---